Skip to main content
Glama

make_captions

Create captions from a transcript and add them to the active editor, timed to a cut edit via planId or an uncut file path. Outputs SRT, VTT, and ASS subtitle files.

Instructions

Create captions from the transcript and add them to the active editor. Pass planId to time captions to the CUT edit (use the same plan you applied), or path for an uncut file. Writes .srt, .vtt and .ass files. Styles: clean (white with outline), bold-pop (big uppercase, active word highlighted), minimal (small boxed).

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": "make_captions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
modelNoWhisper model. "base" (default) is fast; "small"/"medium"/"large-v3-turbo" are more accurate but slower. Downloaded on first use.
styleNoDefault bold-pop
planIdNo
languageNoISO language code such as "en" or "fr"; default auto-detect.
maxCharsNoMax characters per caption (default 32)
maxWordsNoMax words per caption (default 6; use 3-4 for shorts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 real side effects: it writes .srt, .vtt and .ass files and inserts captions into the active editor. However, it omits key behavioral facts for a mutation tool — whether a transcript must already exist or transcription is triggered, whether existing captions are overwritten, and whether an active host/editor is required.

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?

Three compact sentences with the core action front-loaded and the parameter routing immediately after. The trailing style list is somewhat list-like but each descriptor adds information the enum names alone do not convey; nothing is filler.

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

Completeness4/5

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

For a 7-parameter, zero-required mutation tool with no annotations and no output schema, the description covers the action, the two input modes, produced file formats and styling. The notable gap is prerequisites (transcript availability, active editor/host requirement) and any indication of what is returned, which leaves an agent guessing about setup state.

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 coverage is 71% and already documents model, language, maxChars and maxWords. The description compensates for the undocumented parameters by explaining planId (times captions to the applied CUT edit) and path (uncut source file), and adds meaning to the style enum by describing what clean, bold-pop and minimal actually look like.

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 ('Create captions from the transcript and add them to the active editor') and names the concrete artifacts produced (.srt, .vtt, .ass). It is clearly distinguishable from siblings like transcribe or render_caption_overlay, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule between the two source modes: 'Pass planId to time captions to the CUT edit (use the same plan you applied), or path for an uncut file.' That is clear when-to-use guidance for the main branch point, but it offers no exclusions or comparison to alternative caption/transcription tools.

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