Skip to main content
Glama

fablecut_captions

Create timed caption clips from speech transcripts, style them as subtitle, karaoke, highlight, or pop, and export or import SRT and WebVTT subtitles.

Instructions

Captions from what is said: makes caption clips on the timeline from the clips' transcripts (transcribing first when there is none, like fablecut_transcribe), each one a text clip with wordTimes so its words follow the speech. Captions are cut at pauses and sentences, one or two lines as wide as the canvas allows. Styles: subtitle (plain, on a dark bar), karaoke (words light up as they are said), highlight (bold, the word being said in a colour — the reel look), pop (one to three big words at a time, each popping in). They go on the lane captions are already on, else the top video lane, else a new lane above it, and replace the captions there (replace:false keeps them). export:"srt"|"vtt" writes the timeline's captions to a subtitle file in exports/; import: a path to an SRT / WebVTT file (or its text) places its captions instead of the transcript's. remove:true deletes the captions. Captions are text clips: restyle them with updateClip, and make them after the cutting is done (a cut through a caption doesn't re-time its words — run this again). The same as the Transcript tab's Captions row.

Input Schema

NameRequiredDescriptionDefault
toNoOnly speech before this time
fromNoOnly speech from this time on (timeline seconds)
sizeNoScale the style's text size, e.g. 1.2 (default 1)
forceNoAlso replace or remove locked captions (only when the user asked)
linesNoLines per caption, 1–3 (default: the style's)
modelNoTranscribing first: the Whisper model (see fablecut_transcribe)
styleNoThe look (default subtitle)
trackNoThe video lane to put them on (default: chosen as described)
whereNoTranscribing first: where (see fablecut_transcribe)
wordsNoAt most this many words per caption (pop and highlight have their own default)
exportNoWrite the timeline's captions to exports/ as SubRip or WebVTT, and change nothing
importNoAn SRT or WebVTT file (absolute path, or a /media/… src) or its text: place its captions
removeNoDelete every caption clip
clipIdsNoCaption only these clips' speech (default: every clip with sound)
replaceNoRemove the captions already on the timeline first (default true)
languageNoTranscribing first: the spoken language (default: detected)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and does well: it discloses the transcribe-first behavior, lane-placement fallback chain, replacement semantics (replace:false keeps them), and the important caveat that cutting through a caption does not re-time its words. It stops short of stating error conditions or confirmations for the destructive remove path.

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?

Purpose and the core create behavior are front-loaded, and the dense sentences each carry distinct operational facts. It is a long single paragraph, but almost no filler; slightly more structure (splitting mode behavior) would help scanability.

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 16-parameter, no-output-schema, no-annotation tool, the description covers creation, mode switching, lane logic, replacement, and a key timing caveat. Remaining gaps (failure modes, interaction between size/lines/words and style defaults) are minor.

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 100%, so baseline is 3, and the description adds genuine semantics beyond the schema: the lane-selection default logic, export writing to exports/ "and change nothing", and import accepting file path or raw text. These enrich otherwise-documented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("makes caption clips on the timeline from the clips' transcripts") and explicitly anchors itself to the sibling fablecut_transcribe for the transcription path. An agent can distinguish this from fablecut_transcribe and other siblings without opening a schema.

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 clear operating context: transcribe-first fallback, ordering advice ("make them after the cutting is done"), restyling via updateClip, and the equivalent UI row. Modes (export/import/remove) are explained, but it does not state explicit when-not conditions or precedence among modes.

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