Skip to main content
Glama

Make captions

make_captions
Read-only

Timed caption segments for a video of the given length: from the brief (headline, then CTA), from your own text, or parsed from SRT/VTT.

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": {
      "source": "<source>",
      "duration": "<duration>"
    },
    "name": "make_captions"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaNo
textNo
sourceYesbrief: headline then CTA; text: your own copy, split into phrases; subtitles: parse SRT/VTT
durationYesOutput video length in seconds
headlineNo
subtitlesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a non-mutating read/compute operation, so the description only needs to add context. It does add useful behavior - output segments are time-aligned and the duration parameter represents the finished video length - but says nothing about whether caption creation is synchronous or job-based, whether styling applies, or any cost/limit implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence, no filler, with the deliverable stated first and the three input modes listed compactly after it. Every clause maps to actual parameters or output characteristics.

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?

With six parameters and no output schema, the definition should say more about what comes back - the segment structure, units, or whether a style is applied - since 'timed caption segments' is the only hint at return shape. It covers inputs adequately but leaves the agent guessing about output and any post-call workflow.

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 only 33%, so the description has to carry the load, and it does: it explains what headline, cta, text, subtitles, and duration each mean in context (e.g., brief mode puts headline first and CTA after, text is split into phrases, subtitles are SRT/VTT to be parsed). It omits the constraints that the schema enforces itself, such as the 600-second duration ceiling and the maxLength caps, which is acceptable since those live in the schema.

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 deliverable (timed caption segments for a video of a fixed length) and enumerates three distinct input modes tied to the source enum, which separates it from siblings like export_subtitles or edit_transcript. It is a noun phrase rather than a verb, so the action ('make') is only implied by the name, keeping it just short of a 5.

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?

It clearly routes the agent between the three modes: brief-based (headline then CTA), your own text split into phrases, and parsing SRT/VTT. What it does not do is state when to prefer this tool over adjacent siblings such as export_subtitles or edit_transcript, so there is no explicit exclusion guidance.

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