Skip to main content
Glama

Thread Kit: posts that fit every network

Write a timed short-video script (TikTok, Reels, YouTube Shorts) with SRT subtitles (AI) ($0.020)

write_short_video_script
Read-only

Turn an article, notes or product description into a 15/30/45/60-second vertical-video script: hook first, then beats with voiceover, on-screen text and a shot description (usable as a text-to-video prompt), plus title, caption, up to 5 hashtags and SRT subtitles. Timed from speaking rate and trimmed to fit (+10%). No video or voice is generated. A failed generation is not charged. PAID: $0.020 per call in USDC on Base via x402 over MCP, or from prepaid credits if this server is configured with an Authorization: Bearer tkc_... header (see payment_options).

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": {
      "text": "<text>"
    },
    "name": "write_short_video_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of voiceover, on-screen text, title and caption: auto = same as the source (default), or en, zh, zh-TW, ja, ko, es, fr, de, pt, ru, id, vi, tr, it. Shot descriptions are in English.
textYesSource to turn into a script: article, notes or product description (100-3000 characters)
toneNoclear (default), punchy, casual or formal
secondsNoTarget length in seconds: 15, 30 (default), 45 or 60
platformNotiktok (default), reels (Instagram Reels) or shorts (YouTube Shorts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: no video or voice is generated, failed generations are not charged, cost is $0.020 per call via x402/Base or prepaid Bearer credits, and timing derives from speaking rate with a +10% trim. That is strong disclosure for a paid generation call; only latency, concurrency, and the fact that repeated calls may differ (idempotentHint=false) go unmentioned.

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?

One dense but front-loaded paragraph leads with the core transformation and deliverables before pricing, and the payment caveat is confined to a single trailing sentence with a pointer to payment_options. No filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by enumerating the returned components (beats, voiceover, on-screen text, shot description, title, caption, hashtags, SRT). It is nearly complete for a generation tool, with minor gaps only around response format details such as whether SRT arrives as a separate field.

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 3 is the baseline, but the description adds real meaning: it explains that shot descriptions are reusable as text-to-video prompts, that trimming targets +10% of the requested length, and ties the length options to the platform framing. These clarify the effect of seconds/platform/lang beyond the enum lists.

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 transformation (source text -> 15/30/45/60s vertical-video script) and enumerates the exact deliverables: hook, beats, voiceover, on-screen text, shot description, title, caption, hashtags, SRT. An agent can distinguish this from write_thread_from_article or split_thread from the description alone.

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

Usage Guidelines3/5

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

The input shapes the use case (article, notes, or product description into a short-video script), which implicitly tells the agent when to reach for it, and it explicitly redirects to payment_options for billing setup. However, it never states when NOT to use it or contrasts it with the sibling writing tools, so routing relies on inference.

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