Skip to main content
The SocialAPI MCP server gives an AI agent one tool per operation it can run on your SocialAPI account. Every tool name starts with social_api_. A tool runs the same operation as its REST equivalent, so the same scopes, plan allowances, platform support, and error codes apply. An agent calls a tool with a JSON-RPC tools/call request. The arguments are the tool’s input fields:
A tool that fails returns a result with isError: true. When the failure comes from the operation itself, the text is a JSON object with the same code the REST endpoint returns, the message in error, and any meta fields at the top level. This result comes from an API key without the inbox:write scope:
A missing or malformed argument returns a plain-text message instead, for example account_id is required. Every tool except social_api_report_missing_capability also accepts an optional context string argument: the goal the call serves, in one short sentence. Describe people by role, never by name, email, or ID. A call without context runs the same way as a call with it.

Accounts and brands

Comments

See Comments for platform support and limits.

Direct messages

See Direct messages for platform support and the messaging window.

Reviews

See Reviews.

Mentions

See Mentions.

Automations

See Automations.

Posts

See Publishing.

Media

See Media for the upload flow.

Analytics and exports

See Analytics.

Webhooks

See Webhooks.

Events, usage, and your SocialAPI account

What tools do not cover

No tool creates, rotates, or edits an API key, and no tool deletes your SocialAPI account. Create keys in the dashboard or with POST /v1/keys (see Authentication). Among the operations available only through the REST API are:
  • Uploading a file in the request body (POST /v1/media/upload). An agent uploads with social_api_get_media_upload_url instead.
  • Inbox sync, inbound attachments, and message reactions (/v1/inbox/sync, /v1/inbox/media/{id}, /v1/inbox/conversations/{id}/messages/{messageId}/reaction).
  • Creating, editing, and deleting Pinterest boards.
  • The webhook event catalog (GET /v1/webhooks/events). The social_api_create_webhook description lists the event names.
  • Importing posts (POST /v1/posts/import), refreshing an account’s posts (POST /v1/accounts/{id}/sync), announcements (GET /v1/announcements), and the plan catalog (GET /v1/billing/plans).
  • Every endpoint under /v1/platforms/ except Instagram Stories: WhatsApp templates and phone numbers, Google Business Profile locations, platform summaries and insights.

Errors and limits

  • Timeout: a request to the MCP server that runs longer than 5 minutes is stopped.
  • Errors: a failed tool returns isError: true with the same error code as its REST equivalent. Codes are listed in Errors.
  • Scopes: an agent connected with a scoped API key can run only the tools its scopes allow. A tool outside them returns auth.insufficient_scope with the missing scope in required_scope. required_scope is absent for tools that need a full-access key. See Scoped API keys.
  • Cost: a tool call consumes the same credits and plan allowances as its REST equivalent. See Plans.
  • Rate limits: tools that publish or send messages are subject to the same posting and messaging caps as the REST API. See Rate limits.
  • Annotations: every tool declares readOnlyHint, destructiveHint, and openWorldHint. Clients read them to decide which calls need your confirmation.
Last modified on October 17, 2026