Skip to main content
Glama

render_caption_overlay

Render animated captions as a transparent .mov overlay with alpha, timed to your cut edit via planId, so you can place them over footage in any editor.

Instructions

Render animated captions as a transparent video overlay (.mov with alpha) that can be placed over the edit in any editor. Use planId to time it to the cut edit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_caption_overlay"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
pathNo
modelNoWhisper model. "base" (default) is fast; "small"/"medium"/"large-v3-turbo" are more accurate but slower. Downloaded on first use.
styleNoCaption style, e.g. bold-pop, clean, minimal
widthNo
heightNo
outputNo
planIdNo
placeAtNoAlso place the overlay on the timeline at this time (usually 0)
languageNoISO language code such as "en" or "fr"; default auto-detect.
maxWordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral fact: the output is a transparent .mov with alpha rather than a burned-in render. It says nothing about whether a file is written and where, whether it is slow (transcription plus render), or what happens if no plan exists.

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?

Two tight sentences with the output artifact front-loaded and the usage hint second. The clause "that can be placed over the edit in any editor" is somewhat redundant filler but not enough to hurt scanability.

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

Completeness2/5

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

An 11-parameter render tool with no annotations and no output schema needs more than two sentences, particularly since none of the parameters are required and the file-destination behavior is unstated. The description conveys the output format but not enough to invoke correctly without reading every schema field.

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

Parameters2/5

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

Schema coverage is only 36% across 11 parameters, and the description clarifies just one: planId's role in timing to the cut edit. It leaves the most confusing pair — path versus output — completely unaddressed, along with fps, width, height, and maxWords, so an agent must guess which field controls the destination file.

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 names a specific verb ("Render") and a specific artifact ("animated captions as a transparent video overlay (.mov with alpha)"), which distinguishes it from a burn-in caption tool like make_captions or a general render. It never names a sibling directly, so disambiguation relies on inference from the output format.

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?

"Use planId to time it to the cut edit" gives one concrete usage rule, implying the tool is meant to be used after a cut plan exists. There is no statement of when to choose this over make_captions or render, and no prerequisites (existing plan, transcription, media imported) are spelled out.

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