Skip to main content
Glama

Publish a completed video

autoshort_publish_video
Idempotent

Publishes a completed video to connected YouTube, TikTok, Facebook, Instagram, or Threads accounts, handling platform-specific uploads, captions, privacy, and status checks.

Instructions

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 AutoShort"). 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. FACEBOOK / INSTAGRAM / THREADS: publishes publicly as a Facebook Page Reel, an Instagram Reel or a Threads video with your caption (or a default one); #AIGenerated is always added. Meta processes the video for a minute or more: the first call answers QUEUED, call again with the same arguments to read the status (POSTED with the url). A FAILED publish is retried only with retry: true. Idempotent per (videoId, platform): a repeat returns the first result and never posts twice. Respects platform caps (YouTube ≈5 uploads/day; TikTok's pending-drafts limit; Facebook 25, Instagram 25, Threads 50 posts/day). Not connected → NOT_CONNECTED with a connectUrl. 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": "autoshort_publish_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
retryNoFacebook/Instagram/Threads only: publish again after a FAILED attempt (nothing was posted).
titleNoYouTube title (cleaned and cut to 60 characters on a word). Defaults to the video title.
captionNoFacebook/Instagram/Threads caption (Threads ≤500, Instagram ≤2,200 characters and 30 hashtags). Defaults to the video title and topic hashtags.
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 (false except KIDS_SONGS).
userConsentNoTikTok only: the user agreed to send this video to their TikTok drafts.
addAttributionNoYouTube only. Append "Made with AutoShort", a link to autoshort.org and #AutoShort 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 observedv2.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnly=false, openWorld=true, idempotent=true, destructive=false; the description goes far beyond by disclosing platform rate caps (YouTube ≈5/day, Facebook 25, Instagram 25, Threads 50), the QUEUED→POSTED polling protocol, NOT_CONNECTED with a connectUrl, and per-(videoId, platform) idempotency that never double-posts. It also names what is silently added (#AIGenerated, the synthetic-content disclosure, #Shorts) versus what is not (attribution off by default), which is exactly the invisible-mutation detail an agent needs.

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?

Well structured and front-loaded: the one-line purpose, then platform-keyed sections, then cross-cutting rules (retry, idempotency, caps, connection errors). It is dense but every platform block carries distinct behavior; the only minor waste is restating title/description defaults that the schema already documents.

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?

There is no output schema, so the description must explain returns, and it does: QUEUED then POSTED with a url, FAILED, and NOT_CONNECTED with a connectUrl. Combined with the polling, retry, cap, and idempotency rules, an agent has everything needed to call this 10-parameter publish tool correctly on the first attempt.

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 80%, so baseline would be 3, but the description adds genuine semantics for the risky parameters: madeForKids maps to the user's COPPA answer with a niche default, userConsent is a consent gate rather than a plain flag, retry is scoped to FAILED attempts on Meta platforms, and addAttribution carries an explicit default-false policy. These are decision rules the schema text alone does not convey.

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 one of the user's COMPLETED videos") and immediately scopes it by naming the five supported platforms. The capitalized platform labels make it trivially distinguishable from siblings like autoshort_draft_video or autoshort_generate_video 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 Guidelines5/5

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

Gives explicit when-to-use conditions for nearly every conditional branch: pass userConsent only after the user agreed, set addAttribution true only if the user asked for "Made with AutoShort", use retry only after a FAILED attempt, ask the user for the COPPA answer, and call again with identical arguments to poll status. The "COMPLETED" qualifier implicitly excludes the generation/draft siblings.

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