Skip to main content
Glama

subtitles_from_audio

Transcribe timeline audio and generate a subtitle track in DaVinci Resolve Studio, with configurable language, subtitle preset, line breaks, and frame gaps.

Instructions

Auto-caption: transcribe the timeline audio into a subtitle track (Studio). language: auto | english | french | german | spanish | russian | turkish | japanese | korean | mandarin_simplified … ; preset: subtitle_default | teletext | netflix; line_break: single | double; gap in frames.

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

Input Schema

NameRequiredDescriptionDefault
gapNo
presetNosubtitle_default
languageNoauto
line_breakNosingle
chars_per_lineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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. It usefully discloses the Studio availability constraint and enumerates allowed preset values, but says nothing about whether a new subtitle track is created or existing captions are overwritten, how long processing takes, or what happens if the timeline has no audio.

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?

Front-loaded with the purpose, then a compact parameter enumeration with no filler sentences. The telegraphic semicolon style is efficient, though 'gap in frames' is terse enough to border on cryptic.

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?

For a five-parameter, no-annotation, no-output-schema tool that mutates the timeline, the definition covers most parameter values but omits the outcome semantics (new track vs. replacement) and one parameter entirely. Adequate to invoke, incomplete for predicting side effects.

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 coverage is 0%, so the description must compensate. It supplies enum values for language, preset, and line_break that are absent from the schema, plus the unit ('frames') for gap, but chars_per_line is never mentioned and the effect of gap=0 versus a positive value is left unexplained.

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: transcribe timeline audio into a subtitle track, with the 'Auto-caption' framing making the captioning outcome explicit. It does not explicitly differentiate itself from the 'transcribe' sibling, so an agent must infer that this one produces a subtitle track rather than plain text.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The '(Studio)' parenthetical hints at a version prerequisite, but nothing tells the agent when this should be chosen over transcribe or other audio tools.

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