Skip to main content
Glama

Kubeez

generate_dubbing

PRE-FETCH (mandatory): resources/read kubeez://skills/media-upload AND kubeez://skills/billing-confirmation. This is the most expensive model on the platform and Kubeez has no refunds — quote with estimate and get the user's explicit go-ahead before you fire.

Scope: generate:media. Translates and re-voices the speech ALREADY IN a clip, and returns one dubbed .mp4 per language. It does not write music, effects or subtitles, and it does not add speech to a silent clip.

ENGINE (model, default 'sonilo-dubbing'): sonilo-dubbing 17 languages, optional ducking, 10-second billing minimum. elevenlabs-dubbing ElevenLabs, 90+ languages (Romanian included), optional source_language (default 'auto') and cloning_strength (0-10, default 7: how strongly the dubbed voices clone the speakers), a lower per-second rate, no billing minimum. Its full code list is in get_models usage_notes and the model-selection skill. Options of one engine are refused on the other. Compare both with estimate.

INPUT: video_url, https, up to 300 seconds (the provider's own ceiling, lower than the 360 the scoring models take). Local file: get_upload_url(model_id=) → upload → get_upload_session(token) → pass the returned URL. The charge follows the clip length the server measures (duration_seconds never changes it).

LANGUAGES (required, no default). sonilo-dubbing: en, zh_cn, ja, ko, pt, pt_br, es, es_419, de, fr, it, ru, th, ar, tr, vi, id. pt_br is Brazilian Portuguese and es_419 Latin American Spanish; plain pt and es are the unqualified languages, so they are a third option rather than synonyms. ar is unqualified Arabic. Romanian is NOT available on Sonilo. elevenlabs-dubbing: BCP-47 codes such as es, es-MX, pt-BR, fr-CA, ro, pl, hi, 1 to 10 per run, any case and _ or -. ASK the user which languages they want. Do not pick a set for them, because each one is charged in full.

BILLING: clip seconds MULTIPLIED BY the number of languages, at the engine's own per-second rate. Sonilo applies a 10-second minimum to that product (not per language); ElevenLabs has none. Three languages costs three times one. estimate(model=, reference_video_seconds=, variant_count=) is the quote.

DUCKING (sonilo-dubbing only): optional, free, off by default. On, the clip's own music and effects are lowered while the dubbed voice speaks; the bed is kept either way.

ASYNC: returns {generation_id, status:'pending', languages}. Poll get_status(generation_id) — the provider has NO callback, so the poll is also what settles the run and releases any language that was not delivered. Each output's metadata.language names which language it is.

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": {
      "video_url": "<video_url>",
      "languages": "<languages>"
    },
    "name": "generate_dubbing"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNosonilo-dubbing
duckingNo
languagesYes
video_urlYes
source_languageNo
cloning_strengthNo
duration_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the supplied annotations, it discloses exceptional cost, no refunds, per-language multiplication, server-measured billing duration, asynchronous pending responses, and the absence of callbacks. Especially valuable is the warning that polling get_status also settles the run and releases undelivered languages, which is a non-obvious operational side effect.

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?

The critical cost-and-consent warning is front-loaded, and labeled sections make the dense operational guidance easy to scan. The definition is quite long and repeats some billing-minimum and per-language-cost information, although most of the detail is justified by the tool's complexity and absent schema documentation.

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 costly, multi-engine asynchronous tool, it covers the complete invocation path from preflight and approval through upload, parameter selection, quoting, submission, polling, and output-language identification. The output schema further reduces the need for return-value documentation; only minor operational details such as polling cadence are absent.

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?

Despite 0% schema description coverage, the description supplies actionable semantics for all seven parameters, including engine IDs, URL constraints, language-code differences, option defaults and ranges, and engine-specific option rejection. It also clarifies that ducking is free and Sonilo-only and that duration_seconds cannot change the server-measured charge.

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?

The description precisely states that the tool translates and re-voices speech already present in a video, returning one dubbed MP4 per language. It also distinguishes the tool from related generation capabilities by excluding music, effects, subtitles, and adding speech to silent clips.

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?

It gives explicit prerequisites and decision guidance: prefetch two skills, obtain an estimate and explicit approval, ask which languages are wanted, compare engines with estimate, and use the documented upload workflow for local files. Engine-specific capabilities, language availability, exclusions, and billing minima provide concrete criteria for choosing between Sonilo and ElevenLabs.

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