Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

cross_post

Cross-post an EXISTING SupaBird post to LinkedIn, Threads, BlueSky, Instagram, and/or TikTok.

Use this when the post is already scheduled or already live on X. For a brand-new post, use schedule_post with also_post_to instead.

  • Get post_id from get_scheduled_posts (_id).

  • also_post_to: linkedin, threads, bluesky, instagram, tiktok, and/or "all" (every connected+ready network). Instagram requires an image or video. TikTok requires a video or photo.

  • Scheduled posts are queued on the other networks at the same time. Posted posts publish immediately.

  • Skip networks that are already queued/posted, disconnected, over character limit, or coming soon — report those as skipped, do not pretend they posted.

  • Quote posts and trash cannot be cross-posted.

  • TikTok: before posting there, ASK the user who can see it (everyone, friends, followers, or only them) and whether it promotes their brand or is a paid partnership, and tell them "By posting, you agree to TikTok's Music Usage Confirmation". Pass their answers in tiktok. Never choose the visibility for them. TikTok can take a few minutes to process before the post shows on their profile.

  • After publish, ALWAYS show published_urls as clickable links. If a URL is missing, call get_published_urls with this post_id.

  • MCP cannot connect accounts; send the user to Account → My Socials.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "post_id": "<post_id>",
      "also_post_to": "<also_post_to>"
    },
    "name": "cross_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
tiktokNoRequired when TikTok is in also_post_to. Ask the user first; without it TikTok is skipped.
post_idYesThe `_id` of the existing post (from get_scheduled_posts).
also_post_toYesNetworks to add: 'linkedin', 'threads', 'bluesky', 'instagram', 'tiktok', and/or 'all'.
platform_textsNoOptional per-network captions when the original text is too long or should differ.
threads_topic_tagNoOptional Threads topic tag (without #).

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 only say it is a non-read-only, non-idempotent, open-world write; the description goes well beyond that by explaining that scheduled posts are queued at the same time while live posts publish immediately, that unsupported networks must be reported as skipped rather than silently dropped, and that TikTok requires explicit user consent plus a multi-minute processing delay. It also discloses an operational limit the agent cannot otherwise know (MCP cannot connect accounts; direct the user to Account → My Socials).

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 single-sentence purpose followed by tight bullets, each carrying a distinct rule (skip conditions, quote/trash ban, TikTok gating, URL reporting). Dense but every bullet corresponds to a decision the caller must make; it is long only because the tool's contract is genuinely long.

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 5-parameter, nested-object, non-idempotent mutation with no output schema, the description covers prerequisites, per-network constraints, the user-consent flow, failure/skip semantics, and even return-value handling (show published_urls as clickable links, fall back to get_published_urls). Nothing an agent needs to call it correctly is missing.

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, but the description adds real meaning on top: it spells out the accepted also_post_to values including the special 'all' (every connected+ready network), supplies per-network media prerequisites (Instagram needs image/video, TikTok needs video/photo), and frames the tiktok sub-object as an ask-the-user-first workflow. Some of this duplicates the tiktok schema descriptions, which keeps it from a 5.

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?

Uses a specific verb ('cross-post') and a precise resource ('an EXISTING SupaBird post'), names the destination networks, and immediately contrasts itself with schedule_post for brand-new posts. An agent can distinguish it from sibling tools without opening any schema.

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?

States exactly when to use it (post already scheduled or live on X), when not to (new post → schedule_post with also_post_to), where to get post_id (get_scheduled_posts `_id`), and enumerates exclusion cases: quote posts, trash, disconnected or over-limit networks. Alternative routing is explicit rather than inferred.

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