Skip to main content
Glama

Kubeez

generate_captions

PRE-FETCH (mandatory): resources/read kubeez://skills/media-upload AND kubeez://skills/billing-confirmation. Captions are billed per-second — preview cost first.

Caption a video end to end: transcribes the speech, then burns word-timed captions onto the video server-side and returns a finished MP4. Captions are styled automatically and placed to avoid faces, on-screen text, and the main subject. Scope: generate:media. USE 'auto-caption' AS THE MODEL ID EVERYWHERE — upload and estimate both take it, and estimate returns the COMPLETE price in one call. Internally the job bills two per-second lines (speech-to-text, then the burn-in render) and estimate already sums both, itemized under breakdown; do NOT add a second estimate on top or you will double-quote. The render fee is credit-checked BEFORE transcription runs, so an unaffordable job never bills a partial step. Max 30 minutes per video. CANONICAL FLOW: (1) if the user has a local file, call get_upload_url(model_id='auto-caption'). (2) after upload, get_upload_session(token) returns total_video_seconds. (3) estimate(model='auto-caption', reference_video_seconds=<total_video_seconds>) — this is the full price. (4) quote it, ask for go-ahead. (5) only then call this tool. Required: media_url — a public HTTPS URL of the uploaded video. Optional: quality — 'auto' (default, auto-detects language, cheaper) or 'best' (specify a known language for higher accuracy). When quality='best', pass language as one of en/es/fr/de/it/pt. Optional: code_switching — true if the video mixes multiple spoken languages in one track. Optional manual placement (defaults to automatic content-aware placement): caption_x / caption_y — percent offsets of the caption block's center from the video center (x negative = left, y positive = down; y=18 is the standard lower zone); caption_scale — absolute caption size multiplier. Pass these ONLY when the user positioned the captions themselves. Async: returns {generation_id, status: 'processing', credits_charged} immediately. Poll get_generation(generation_id) until the captioned video appears in outputs.

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": {
      "media_url": "<media_url>"
    },
    "name": "generate_captions"
  }
}

Input Schema

NameRequiredDescriptionDefault
qualityNoauto
languageNo
caption_xNo
caption_yNo
media_urlYes
caption_scaleNo
code_switchingNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses billing mechanics (two per-second line items summed by estimate), credit-check ordering before transcription, the 30-minute cap, and the async contract returning {generation_id, status, credits_charged} for polling. These are exactly the operational details annotations cannot express.

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?

It is front-loaded with the mandatory pre-fetch and follows a numbered flow, which is highly scannable. It is long and repeats the double-quote warning idea twice ('do NOT add a second estimate' and 'you will double-quote'), which costs some tightness, but nearly every sentence carries operational content.

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 7-param mutating, billed, async tool, the description covers prerequisites, cost preview, scope, limits, return shape, and polling — more than enough even though an output schema exists. Nothing an agent needs in order to invoke it correctly 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 0% – the schema carries only titles and defaults, with no enums declared – so the description must compensate, and it mostly does: it explains 'auto' vs 'best', supplies the language set en/es/fr/de/it/pt, defines code_switching, and gives sign conventions for caption_x/caption_y plus the y=18 convention. The gap is that media_url's constraints, quality/language defaults, and the non-obvious interaction of language with quality='auto' are only partially pinned down.

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 gives a specific verb and resource with full scope: 'Caption a video end to end: transcribes the speech, then burns word-timed captions onto the video server-side and returns a finished MP4.' It also names the adjacent tools (estimate, get_upload_url, get_generation) so an agent can separate this from the estimate/upload steps without inspecting schemas.

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 lays out an explicit CANONICAL FLOW with preconditions and ordering (upload → session seconds → estimate → user go-ahead → this tool), states a negative rule ('do NOT add a second estimate'), and constrains optional params ('Pass these ONLY when the user positioned the captions themselves'). Both when-to-use and when-not-to-use are covered.

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