Skip to main content
Glama
miracleweasel

katto-mcp

by miracleweasel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

katto_dub_clip

Re-render a finished clip dubbed into one or more of 19 languages without using your monthly video quota. Returns a rerender_id to poll for the result.

Instructions

Re-render one finished clip dubbed into one or more of 19 languages (en, es, fr, it, pt, hi, ja, zh, de, ko, nl, pl, ru, tr, id, vi, th, uk, ar). 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.

Input Schema

NameRequiredDescriptionDefault
idYesJob id.
languagesYesTarget languages for the dub, as ISO 639-1 codes. Nineteen are available; 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.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."
  2. 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"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly=false, idempotent=false, destructive=false); the description adds substantive context on top: each call starts a NEW render and is explicitly not idempotent, it consumes no monthly video quota, it requires an active subscription, and it hands back a rerender_id that must be polled. Those are exactly the behavioral facts an agent cannot get from the annotations.

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?

Four short sentences, front-loaded with the core action and language scope, then entitlement, then idempotency, then the polling contract. Nothing is redundant and the ordering matches the order an agent needs the information.

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 three-parameter mutation tool with no output schema, the description covers the return value (rerender_id), the required follow-up call (katto_get_rerender), entitlement requirements, and repeat-call semantics. Combined with the fully documented schema and the annotations, nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and includes the enum and the 'original audio retained for unlisted languages' note, so the schema already carries parameter meaning. The description merely restates the 19-language list, adding no syntax, indexing, or format detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Re-render one finished clip dubbed into ... 19 languages') with explicit scope (one clip, one-or-more languages), which is far clearer than the bare name. It does not, however, differentiate itself from the sibling katto_rerender_clip, and its opening word 'Re-render' actually echoes that sibling's name, so an agent still has to infer the boundary.

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?

It gives useful operating context — creator feature, active subscription required, no monthly quota consumption — and routes the agent forward to katto_get_rerender for the result. What it never states is when to pick this tool over katto_rerender_clip or katto_translate_captions, nor any precondition about the source clip being finished/previous job state.

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

Deploy Server

Other Tools