Skip to main content
Glama

Publish or schedule a post

publish_post
DestructiveIdempotent

Posts a ready video to your connected accounts now, at a time (mode schedule), or in the profile queue. Only after preview_post passed and the user agreed: confirm must be true. For TikTok, pass the tiktok.privacy_level the user chose. idempotency_key: a new unique string per intended post. Repeat the same call with the same key only when it did not answer (timeout, network): you get the same post back, never a second one. A post that came back failed needs a new key; the same key with different arguments is refused (idempotency_mismatch). Counts one post per account against your plan.

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": {
      "video_id": "<video_id>",
      "profile_id": "<profile_id>",
      "account_ids": "<account_ids>",
      "caption": "<caption>",
      "mode": "<mode>",
      "confirm": "<confirm>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "publish_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes'now', 'schedule' (needs scheduled_at) or 'queue' (the profile's next free slot)
titleNoTitle for titled networks (YouTube); required when one is targeted
redditNoRequired when a Reddit account is targeted
tiktokNoTikTok settings, used when a TikTok account is targeted. Ask the user who can view it (privacy_level) before preview_post.
captionYesPost text on every network (on YouTube: the description)
confirmYesMust be true: the user agreed to publish
timezoneNoIANA zone, e.g. Europe/Madrid (default: the server default)
video_idYesA ready video (list_videos / get_video status "ready")
overridesNoPer network (tiktok, instagram, youtube, facebook, linkedin, threads, reddit, bluesky): a different caption and, on titled networks (YouTube), a different title. Networks left out use caption / title.
profile_idYesThe profile to post from (list_profiles)
account_idsYesAccounts of that profile to post to (list_profiles, postable: true)
ai_generatedNoLabel the post as AI-generated where the network supports it (default: true for AI swaps, false for your own videos)
scheduled_atNoLocal time YYYY-MM-DDTHH:mm in `timezone`
first_commentNoPosted as the first comment where the network supports it
idempotency_keyYesA new unique string per intended post
youtube_privacyNoYouTube visibility (default public)

Output Schema

NameRequiredDescriptionDefault
idYes
statusYes
app_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint and idempotentHint, but the description goes well beyond them: it explains the exact retry contract (same key only after a timeout/network non-answer; a failed post needs a new key), the mutation-cost model (one post per account against the plan), and the TikTok privacy prerequisite. That is precisely the operational context annotations cannot express.

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

Conciseness5/5

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

Front-loaded with the action and the confirmation gate, then layers retry rules and plan cost. Sentences are dense but every one carries a distinct operational fact with no 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 16-parameter, nested, multi-network mutation with a destructive profile, the description covers the gating workflow, the idempotency contract, cost, and the one required user decision. Return values are covered by the output schema, so nothing essential 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; the description earns an extra point by adding retry semantics to idempotency_key and by restating the hard confirm gate as a workflow rule rather than a type constraint. Its TikTok privacy guidance largely duplicates what the tiktok.privacy_level schema already says, so it is not fully additive.

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 ('Posts a ready video to your connected accounts') and immediately enumerates the three modes: now, schedule, queue. It distinguishes itself from the sibling preview_post by naming it as a prerequisite gate rather than an alternative.

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 an explicit precondition ('Only after preview_post passed and the user agreed: confirm must be true') and routes mode selection with concrete conditions (schedule needs scheduled_at, queue uses the profile's next free slot). It also names the refusal case (idempotency_mismatch) so the agent knows what not to do.

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.