Skip to main content
Glama

add_captions

Add burned-in captions to AI-generated video clips, timed automatically to voice lines or spread from custom text, with style, position, word count, and highlight options.

Instructions

Burned-in captions. text "auto" = timed to the voice line put on with add_voice (edge voices). Or your own text, spread over the clip ("|" forces a break). style: bold | impact | clean | box. position: bottom | lower | center | top. highlight = yellow text.

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": "<video>"
    },
    "name": "add_captions"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoauto
styleNobold
videoYes
positionNobottom
highlightNo
words_per_captionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world operation, so the safety bar is partly covered. The description adds genuinely useful behavior beyond that: the captions are burned in (rendered into the video, not a separate track) and the "|" character forces a line break. It does not say whether an existing caption layer is replaced on re-run or what the call returns.

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?

Very compact, front-loads the core concept, and each clause adds a distinct fact (text mode, style, position, highlight) with no filler. The telegraphic fragment style and the missing verb at the start cost a little readability.

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

Completeness3/5

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

For a 6-parameter mutation with no output schema and no schema-level parameter docs, the description covers four of six parameters and the core behavior, which is close to sufficient. It still leaves words_per_caption and the video parameter unexplained, and does not address idempotency or return values.

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 description coverage is 0% across 6 parameters, so the description must carry the load and it largely does: it defines text="auto" vs. custom text with "|" as a forced break, enumerates the four style presets (bold | impact | clean | box), the four positions (bottom | lower | center | top), and explains highlight as yellow text. Only video and words_per_caption remain undocumented, so the 0% coverage gap is mostly closed.

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?

"Burned-in captions" plus the explanation of auto-timed-to-voice vs. custom text makes it clear this tool renders subtitle text onto a clip. It is specific about the resource and the two text modes, but never uses an explicit verb and never distinguishes itself from the sibling add_text, leaving the caption-vs-text boundary to inference.

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?

The description implies a usage path: text="auto" is timed to the voice line previously added with add_voice (edge voices), otherwise your own text is spread over the clip. That is real conditional guidance, but there is no statement of when not to use it, no prerequisites (does add_voice have to run first?), and no comparison with add_text.

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