Skip to main content
Glama

katto_dub_clip

Re-render a finished clip with dubbing in one or more of 105 languages, starting a new render and returning a rerender_id to poll for the result.

Instructions

Re-render one finished clip dubbed into one or more of 105 languages (ISO 639-1 codes such as en, es, fr, pt, hi, bn, ta, te, ur, ja, zh, ko, ar, sw; 86 of them in beta). Creator feature (requires an active subscription); does NOT use your monthly video quota. Each call starts a new render (not idempotent). Returns a rerender_id; poll katto_get_rerender for the result.

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": {
      "id": "<id>",
      "clip_index": "<clip_index>",
      "languages": "<languages>"
    },
    "name": "katto_dub_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob id.
languagesYesTarget languages for the dub, as ISO 639-1 codes. 105 are available, 86 of them in beta; the clip keeps its original audio for any language not listed here.
clip_indexYes0-based clip index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.2
    • changedInput schema / properties / languages / description
      Previous value: -"Target languages for the dub, as ISO 639-1 codes. Nineteen are available; the clip keeps its original audio for any language not listed here."New value: +"Target languages for the dub, as ISO 639-1 codes. 105 are available, 86 of them in beta; the clip keeps its original audio for any language not listed here."
  2. Changed1 schema field changedv0.6.1
    • addedInput schema / properties / languages / description
      Added value: +"Target languages for the dub, as ISO 639-1 codes. Nineteen are available; the clip keeps its original audio for any language not listed here."
  3. Changed1 schema field changedv0.5.9
    • changedInput schema / properties / languages / items / enum
      Previous value: -[
      -  "en",
      -  "es",
      -  "fr",
      -  "it",
      -  "pt",
      -  "hi",
      -  "ja",
      -  "zh"
      -]New value: +[
      +  "en",
      +  "es",
      +  "fr",
      +  "it",
      +  "pt",
      +  "hi",
      +  "ja",
      +  "zh",
      +  "de",
      +  "ko",
      +  "nl",
      +  "pl",
      +  "ru",
      +  "tr",
      +  "id",
      +  "vi",
      +  "th",
      +  "uk",
      +  "ar"
      +]
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare idempotentHint=false and readOnlyHint=false, but the description goes well beyond them: it explains WHY re-calls duplicate work ('each call starts a new render'), discloses the subscription gate, notes quota is unaffected, and hands the agent the async follow-up path (rerender_id then katto_get_rerender). That is exactly the context annotations cannot carry.

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?

Three dense sentences, no filler, with the capability statement first, then the gating/quota caveats, then the async return contract - front-loaded and easy to scan.

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 mutating, non-idempotent, subscription-gated render tool with no output schema, the description supplies everything an agent needs: cost implications, duplicate-call risk, return value, and the polling tool. Nothing material is left unstated.

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 baseline is 3; the description earns extra by naming the ISO 639-1 convention with concrete examples and by stating that unlisted languages keep the original audio. It does not clarify id or clip_index beyond the schema, and its '105 languages' claim sits oddly against the schema's 19-value enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource+scope: 'Re-render one finished clip dubbed into one or more of 105 languages.' That is far more precise than the sibling katto_rerender_clip's likely generic framing, though the description never names that sibling to draw the contrast explicitly.

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?

It states clear operating conditions: creator feature requiring an active subscription, does not consume monthly video quota, and each call starts a new render. What is missing is an explicit 'use X instead when...' routing rule versus katto_rerender_clip or katto_translate_captions.

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