Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

get_connected_socials

Read-onlyIdempotent

List the user's connected social accounts for cross-posting: X, LinkedIn, Threads, BlueSky, Instagram, and TikTok.

Call this BEFORE scheduling to other networks, or when the user asks what is connected / why a network failed.

Returns ready vs disconnected vs needs_reconnect, character limits, and coming-soon platforms (YouTube, Facebook, Pinterest). Instagram requires an image or video. TikTok requires one video or JPEG/WebP photos. Neither supports threads.

If a network is missing or needs reconnect, tell the user to open Account → My Socials. MCP cannot connect accounts.

With several social sets, accounts are grouped by set (each set is one brand). Pass social_set to see one set. Facebook shows as connected in the app but can't be posted to from the chat yet.

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": "get_connected_socials"
  }
}

Input Schema

NameRequiredDescriptionDefault
social_setNoOnly this social set's items: its name, id or one of its handles. Omit for every set.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it describes the status taxonomy (ready vs disconnected vs needs_reconnect), included metadata like character limits, coming-soon platforms, media requirements per network, and the hard limit that MCP cannot connect accounts.

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 the purpose and the timing rule, then layered detail. It is dense rather than padded, though the media-requirement and Facebook-quirk lines make it longer than strictly needed for tool selection.

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?

No output schema exists, but the description compensates by summarizing return contents (statuses, limits, coming-soon platforms) and documenting edge cases like Facebook and Instagram/TikTok media constraints, leaving nothing critical unstated.

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 100%, so the baseline is 3; the description adds real meaning by explaining that accounts are grouped by social set and that each set represents one brand, clarifying what social_set selects.

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?

Opens with a specific verb and resource ('List the user's connected social accounts for cross-posting') and enumerates the covered platforms, so the agent knows exactly what this returns and how it differs from analytics/timeline siblings.

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?

Gives explicit timing rules ('Call this BEFORE scheduling to other networks') and two concrete trigger conditions (user asks what is connected, or asks why a network failed), plus a fallback action when a network is missing.

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

All SupaBird toolsInspect
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.

Resources