Skip to main content
Glama

Burn In Subtitles

burn_subtitles
Destructive

Embed SRT/ASS subtitle files into a video using bundled fonts, with optional clean or social styling, so transcribed captions are visible in the final recording.

Instructions

Burn SRT/ASS subtitles (e.g. from transcribe) into a video in the bundled font.

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": {
      "input": "<input>",
      "subtitles": "<subtitles>"
    },
    "name": "burn_subtitles"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the source video.
styleNoclean (default for .srt): outlined line. social: big bold text on a dark box. .ass keeps its own styling unless set.
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
overwriteNoAllow replacing an existing file at the output path (default false).
subtitlesYesPath to an .srt (e.g. from transcribe) or .ass subtitle file.

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.47.0
    • changedInput schema / properties / style / description
      Previous value: -"'clean' (default): a modest outlined line. 'social': large bold text on a dark box, for muted autoplay."New value: +"clean (default for .srt): outlined line. social: big bold text on a dark box. .ass keeps its own styling unless set."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "outputPath": {
      +      "description": "Path of the file written.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "outputPath"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the risk profile is covered. The description adds only the 'bundled font' constraint (styling is fixed, not user-supplied), and says nothing about whether the source video is preserved or how overwrite protection behaves — though the schema covers the latter.

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 naming the action, the input formats, and the styling constraint; nothing redundant. The mention of the source tool is a compact, useful workflow cue rather than filler.

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 an output schema and full parameter documentation, the essentials are covered. However, for a destructive, non-idempotent media write, the description omits whether the input video is left untouched and what happens when subtitles cannot be parsed or the chosen style conflicts with .ass styling — gaps the structured fields don't close.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including the style enum's meaning and the output/overwrite defaults, so the schema does the heavy lifting. The description adds almost nothing parameter-level beyond reinforcing accepted subtitle formats, which the schema already states — baseline 3.

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: burn subtitles (SRT/ASS) into a video. The parenthetical '(e.g. from transcribe)' ties it to the upstream sibling, so the agent can place it in a workflow, though it does not explicitly contrast with adjacent post-processing tools like overlay or title_card.

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 reference to transcribe implies a when-to-use context (caption burn-in after transcription), but there is no explicit statement of when to prefer this over overlay/title_card, nor any prerequisite or exclusion.

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