Post Bridge

list_social_accounts

Read-only

List the user's connected social media accounts across Instagram, TikTok, YouTube, X (Twitter), LinkedIn, Facebook, Pinterest, Threads, Bluesky, and Google Business Profile. Returns account IDs, platforms, usernames, needs_reconnect, and has_x_premium (X accounts only: true means posts can be up to 25,000 characters instead of 280). When needs_reconnect is true, repeated dead-token failures have paused posting to that account: posts to it are skipped until the user reconnects it in the dashboard (reconnecting clears it automatically). Do not post or retry against accounts in that state; tell the user to reconnect instead. Each account also carries workspace_id and workspace_name, the dashboard workspace it sits in (workspace_id null = the default "Main" workspace). Users often keep one workspace per brand or client: when they name a workspace, brand or client, post only to the accounts in that workspace, never to every account on the platform. Pass workspace_id (or "main") to list just one workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_social_accounts"
  }
}

Input Schema

Name	Required	Description	Default
`workspace_id`	No	Only list accounts in this workspace: a workspace_id from a previous list_social_accounts call, or "main" for the default workspace. Omit to list every account.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / workspace_id

Added value: +{
+  "description": "Only list accounts in this workspace: a workspace_id from a previous list_social_accounts call, or \"main\" for the default workspace. Omit to list every account.",
+  "type": "string"
+}

First observedSep 9, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint, it discloses that needs_reconnect means dead-token failures have paused posting, that reconnecting in the dashboard clears it automatically, and that workspace_id null maps to the default "Main" workspace. It also explains has_x_premium's consequence (25,000 vs 280 characters) so the agent understands downstream posting behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and return fields, then the needs_reconnect rule and workspace semantics; the ordering is sensible. Slightly dense — the 25,000 vs 280 character detail and the reconnect explanation could be tightened — but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, one-parameter lister with no output schema, the description covers return fields, the meaning of every flag, and how to scope by workspace. An agent has everything needed to call it and interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: workspace_id accepts "main" for the default workspace, omitting it lists every account, and workspace_id/workspace_name reflect dashboard workspaces that typically map to one brand or client. Minor gap: it does not say where a valid workspace_id comes from beyond the schema's note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the user's connected social media accounts"), enumerates the platforms covered, and names the exact return fields (account IDs, platforms, usernames, needs_reconnect, has_x_premium). This clearly separates it from siblings like list_posts or list_analytics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly handles the key branch: when a user names a workspace/brand/client, post only to accounts in that workspace, never every account on the platform. It also gives a hard prohibition (do not post or retry against needs_reconnect accounts; tell the user to reconnect) and explains when to pass workspace_id versus omit it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Post Bridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.