Skip to main content
Glama

Publish a video

publish_video
Idempotent

Publish one of the user's COMPLETED videos. YOUTUBE: uploads to the connected channel with your title/description and privacy (public, unlisted, private); the "altered or synthetic content" disclosure is always set; madeForKids is the user's COPPA answer (ask them for a kids audience); nothing is appended to the description unless addAttribution is true (default false — only when the user asked for "Made with StoryShort"). TIKTOK: sends the video to the creator's TikTok Drafts (inbox) — they add the caption, switch on the AI-generated label and post in the app; pass userConsent: true only after the user agreed. Idempotent per (videoId, platform): a repeat returns the first result and never posts twice (a video already posted from the website counts). Respects platform caps (YouTube ≈5 uploads/day; TikTok's pending-drafts limit). Not connected → NOT_CONNECTED with a connectUrl. Requires the "video:create" scope. Free.

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": {
      "videoId": "<videoId>",
      "platform": "<platform>"
    },
    "name": "publish_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoYouTube title (cleaned and cut to 60 characters on a word). Defaults to the video title.
privacyNoYouTube visibility (default public).
videoIdYes
platformYes
descriptionNoYouTube description. #Shorts is added if missing.
madeForKidsNoYouTube COPPA declaration. Omit to use the series answer, or the niche default.
userConsentNoTikTok only: the user agreed to send this video to their TikTok drafts.
addAttributionNoYouTube only. Append "Made with StoryShort", a link and #StoryShort to the description. Default false: set true ONLY if the user explicitly asked for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes far beyond the annotations: it discloses idempotency keying per (videoId, platform) with repeat-returns-first-result semantics, platform rate caps (YouTube ~5/day, TikTok pending-drafts limit), implicit description mutations (#Shorts appended, altered/synthetic disclosure always set), auth scope, and the structured NOT_CONNECTED failure with connectUrl. This is exactly the side-effect and limit information an agent needs for an irreversible external post.

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 idempotency, then platform-labeled sections, so it's scannable despite being a dense run-on paragraph. A few clauses (e.g. the altered-content disclosure detail) are verbose, and bullet/list structure would read better, but nothing 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 an 8-parameter, open-world, non-reversible publish action with no output schema, the description covers preconditions, per-platform divergence, idempotency, limits, failure mode, and consent semantics. An agent could invoke this correctly and safely from the description alone.

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?

With 75% schema coverage the baseline is 3, but the description adds real meaning: madeForKids is framed as the user's COPPA answer tied to series/niche defaults, addAttribution is conditioned on the user's wording, and userConsent is a consent gate rather than a plain flag. It also clarifies privacy and title are YouTube-only.

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 ("Publish one of the user's COMPLETED videos") plus the completion precondition, then splits behavior per platform (YOUTUBE upload vs TIKTOK drafts inbox). An agent can tell exactly what happens on each platform 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 strong conditional guidance: pass userConsent only after agreement, ask the user for a kids audience, set addAttribution only on explicit request, and the NOT_CONNECTED/scope prerequisites. The one gap is that it never routes the agent away from this tool toward a sibling (e.g. draft_video or render_draft) when a video isn't finished.

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.

Resources