Skip to main content
Glama

AIClipMaker.org

Burn styled captions onto a clip

add_subtitles

Re-style the captions of one clip (clips already ship with the 'default' preset). Easiest: pass a preset; any other field you send overrides that part of it. Without a preset, style 'karaoke' highlights the active word.

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": {
      "job_id": "<job_id>",
      "clip_index": "<clip_index>"
    },
    "name": "add_subtitles"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo
effectNoKaraoke active-word effect; 'highlight' = solid box behind it.
job_idYes
presetNodefault: Anton caps, yellow active word. hormozi: words appear as spoken, yellow active word. pill: purple box behind the active word. lime: lime box behind the active word. oneword: one big word at a time. clean: no outline, soft shadow, sentence case.
revealNoKaraoke: words appear as they are spoken.
shadowNoDrop shadow depth 0-6.
one_wordNoShow one word at a time.
positionNo
font_nameNoAnton, Montserrat ExtraBold, Verdana, Arial, Impact, Georgia...
font_sizeNo44 is the default (M); 34 = S, 56 = L, 70 = XL.
uppercaseNo
clip_indexYes0-based index from list_clips.
font_colorNoHex color, e.g. #FFFFFF.
border_widthNoOutline 0-10 (0 needs a shadow to stay readable).
highlight_colorNoKaraoke active-word color (or box color with effect 'highlight').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive, closed-world operation. The description adds useful behavior around presets and overrides, plus the default-preset baseline. It does not disclose what happens to existing captions, whether a render/job is triggered, or what the response contains, which is a gap for a styling mutation.

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, front-loaded with purpose, then the preset shortcut, then the no-preset default. Nearly every sentence earns its place, though the phrase 'overrides that part of it' is slightly imprecise.

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 15 parameters, no output schema, and annotations covering only basic safety, the description should do more. It covers the key preset/override behavior well, but it omits what the tool returns, whether it is asynchronous, and what happens to prior caption styling.

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 73%, so most parameters are documented structurally. The description adds genuinely non-obvious meaning beyond the schema: passing a preset establishes a baseline and any other field overrides just that part, and without a preset the style defaults toward karaoke active-word highlighting. It leaves some parameters to the schema, but the added interaction rule is valuable.

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: re-style the captions of one clip. It also notes clips already ship with the default preset, which clarifies the tool's role. It does not explicitly distinguish itself from siblings such as recut_clip or process_video, so it stops short of 5.

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?

Offers configuration guidance: pass a preset for the easiest path, and other fields override the preset. It also explains the no-preset default. However, it does not say when to choose this tool over alternatives like recut_clip or process_video, nor does it state prerequisites.

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