Blotato vs Publer API + MCP

Blotato

One paid account gives an agent a REST API with a public OpenAPI document and an MCP server with 36 tools, with request limits and error codes documented in detail. No status page, changelog, security contact or free API access was found, and each account has a single key with full access.

Publer API + MCP

Scoped API keys (workspaces, accounts, posts, media, analytics) with 401 and 403 errors that name the missing scope or header. API and MCP only on Business and Enterprise, and the free plan has no API.

Blotato

1. Call blotato_list_accounts or GET /v2/users/me/accounts first, and fetch pageId or boardId before posting to a Facebook Page, LinkedIn company Page or Pinterest
2. Keep the postSubmissionId and poll the status until published, scheduled or failed. It is a receipt, not proof of publication
3. After a timeout on a create call, list existing posts before sending again, because there is no idempotency key
4. Do not generate an API key on a trial account unless the owner accepts the Starter charge
5. Keep REST bodies and MCP arguments apart. REST nests post.content and post.target, and the MCP tool takes flat arguments

Publer API + MCP

1. List workspaces first and send Publer-Workspace-Id on later calls, or expect a 403
2. Poll /job_status/{job_id} after posts/schedule and read payload.failures, since status reads complete even when posts failed
3. Use the Bearer-API scheme, not Bearer
4. Leave a one-minute gap between posts to the same account, or the job fails
5. Read X-RateLimit-Reset after a 429 and wait until then, as there's no Retry-After