Skip to main content
Glama

posts_publish

Destructive

Publish a post (or a video) on a connected account: Instagram, YouTube, TikTok, X, Threads, LinkedIn, Facebook (a Page) or Skool. Name the account with account_id (from channels.list), or name only the channel when the workspace has one account there. What a post may carry differs by channel and the answer says what was refused: YouTube and TikTok take one video, Instagram one image, one video (a Reel), 2-10 images (a carousel) or, with options.media_type "story", one image or video as a story (no text, alt_text, location_id or share_to_feed), X up to 4 media, LinkedIn one image (up to 20 MB) or one video (up to 100 MB), Facebook text with a link, up to 10 images or one video. Publish only when the user explicitly asks for this post: it is public and cannot be taken back. A failure of type outcome_unknown may already be live: check before publishing again.

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

Input Schema

NameRequiredDescriptionDefault
textNoThe post's text: a caption, a description, a tweet, a post body.
titleNoA title, for channels whose posts have one (YouTube, Skool; TikTok uses text).
channelNoThe channel, when account_id is omitted and the workspace has one account on it (instagram, youtube, tiktok, x, threads, linkedin, facebook, skool).
optionsNoThe channel's own settings, e.g. YouTube {tags, category_id, made_for_kids}, TikTok {disable_comment, disable_duet, disable_stitch, brand_content_toggle, brand_organic_toggle}, Instagram {alt_text, location_id, share_to_feed, media_type (auto|image|reels|story)}, Threads {reply_control, alt_text}, Facebook {link, scheduled_at (ISO 8601 with offset, 10 minutes to 30 days ahead)}. An option the channel does not have is refused.
audienceNoWho sees it. OMIT for the channel's default. YouTube: public, unlisted, private; TikTok: public, friends, followers, private; LinkedIn: public, connections.
reply_toNoA post of this account to answer (a thread of posts on X or Threads).
account_idNoThe account that publishes (its id from channels.list).
destinationNoWhere inside the account it goes, when the channel has places: a Skool community id.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
media_file_idsNoWorkspace files to attach, in order (ids from files).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / options / description
      Previous value: -"The channel's own settings, e.g. YouTube {tags, category_id, made_for_kids}, TikTok {disable_comment, disable_duet, disable_stitch, brand_content_toggle, brand_organic_toggle}, Instagram {alt_text, location_id, share_to_feed}, Threads {reply_control, alt_text}, Facebook {link, scheduled_at (ISO 8601 with offset, 10 minutes to 30 days ahead)}. An option the channel does not have is refused."New value: +"The channel's own settings, e.g. YouTube {tags, category_id, made_for_kids}, TikTok {disable_comment, disable_duet, disable_stitch, brand_content_toggle, brand_organic_toggle}, Instagram {alt_text, location_id, share_to_feed, media_type (auto|image|reels|story)}, Threads {reply_control, alt_text}, Facebook {link, scheduled_at (ISO 8601 with offset, 10 minutes to 30 days ahead)}. An option the channel does not have is refused."
  2. Changed2 schema fields changed
    • changedInput schema / properties / channel / description
      Previous value: -"The channel, when account_id is omitted and the workspace has one account on it (instagram, youtube, tiktok, x, threads, linkedin, skool)."New value: +"The channel, when account_id is omitted and the workspace has one account on it (instagram, youtube, tiktok, x, threads, linkedin, facebook, skool)."
    • changedInput schema / properties / options / description
      Previous value: -"The channel's own settings, e.g. YouTube {tags, category_id, made_for_kids}, TikTok {disable_comment, disable_duet, disable_stitch, brand_content_toggle, brand_organic_toggle}, Instagram {alt_text, location_id, share_to_feed}, Threads {reply_control, alt_text}. An option the channel does not have is refused."New value: +"The channel's own settings, e.g. YouTube {tags, category_id, made_for_kids}, TikTok {disable_comment, disable_duet, disable_stitch, brand_content_toggle, brand_organic_toggle}, Instagram {alt_text, location_id, share_to_feed}, Threads {reply_control, alt_text}, Facebook {link, scheduled_at (ISO 8601 with offset, 10 minutes to 30 days ahead)}. An option the channel does not have is refused."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructive/non-idempotent/open-world, but the description adds real context beyond them: the post is public and irreversible, per-channel media limits and size caps, that unsupported options are refused in the response, and that an outcome_unknown failure may already be live so the agent should check before retrying.

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 irreversible-warning language, and each sentence carries content. The channel-by-channel media enumeration is dense and long, but it is load-bearing rather than 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 10-parameter destructive publish tool with no output schema, the description covers intent gating, channel constraints, refusal reporting, and retry hazards. Nothing an agent needs to avoid a bad publish is missing.

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

Parameters5/5

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

Schema coverage is 100%, yet the description still adds cross-parameter meaning the schema does not state: the channel-vs-account_id fallback, which channels accept video vs carousel vs story, and that media_type "story" forbids text, alt_text, location_id and share_to_feed. This is genuine constraint knowledge beyond the field-level descriptions.

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 ("Publish a post (or a video) on a connected account") and enumerates the exact channels covered. An agent can tell this apart from posts_delete or draft-approval tools without opening the schema.

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

Usage Guidelines4/5

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

Gives an explicit gate ("Publish only when the user explicitly asks for this post") plus the account-addressing fallback rule (account_id from channels.list, else channel when the workspace has one account). It stops short of naming an alternative path such as approving a draft, so it is clear context without full routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.