Accounts tools
The list_accounts tool: every account an API key can reach, its type and whether it may make changes.
Needs: Always available. 1 tool.
Every MCP server has this tool, whatever it is connected to, so every API key can call it. Send its arguments as a JSON object. See Calling tools for the request and response format.
Call it first: the id of each account is what other tools take as their account argument. If the MCP server has only one account of a kind, you can leave account out of those tools.
An example answer (shortened):
{
"data": [
{ "id": "google-analytics", "label": "Acme Ltd", "type": "marketing", "provider": "google_analytics", "changes": "read-only" },
{ "id": "zendesk", "label": "Acme Support", "type": "helpdesk", "provider": "zendesk", "site": "acme.zendesk.com", "changes": "off (read-only)" }
]
}
Each account says whether it may make changes. Mailboxes have sending (on, paused or off (drafts only)). Zendesk and calendars have changes (on, paused or off (read-only)). Marketing, contacts, stores and Mailchimp always say read-only.
| Tool | What it does | Kind |
|---|---|---|
list_accounts |
List connected accounts | Read |
list_accounts
List connected accounts · Read
Lists the accounts this MCP can use (mailboxes such as Gmail, Outlook, iCloud; helpdesks such as Zendesk; marketing logins for Google Search Console/Analytics/Ads, Microsoft Advertising, Tag Manager, YouTube and Merchant Center; Google Drive and Sheets; Google, iCloud or Outlook Calendar and Contacts; WooCommerce and Magento stores; Mailchimp), their type, and whether each may send or make changes. Use the returned id in other tools.
No arguments: send {}.
Example request:
curl -X POST https://app.plugsight.app/v1/tools/list_accounts \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'