Skip to main content
Glama

Subtitles

subtitle
Read-only

Generate SRT/VTT subtitles from audio or video. Returns the subtitles as SRT or VTT text with the language, duration and number of cues. Use to caption a video or an audio file. For a plain transcript use stt or transcribe. Cost: 2 credits, charged only when a call succeeds.

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": {
      "audio_url": "<audio_url>"
    },
    "name": "subtitle"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoSubtitle format.srt
languageNoLanguage code.en
audio_urlYesURL to audio/video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered; the description goes further by disclosing the billing model (2 credits, charged only on success), which no structured field carries and which materially affects retry decisions. It also describes the return payload (SRT/VTT text with language, duration and cue count), compensating for the absent output schema.

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?

Three tight sentences, each carrying distinct information: capability, return shape, usage routing, then cost. The most decision-relevant facts (what it does, when to prefer it) are front-loaded with zero filler.

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 read-only, three-parameter tool with no output schema, the description covers purpose, alternative routing, return contents and cost — enough to call it correctly. Minor gaps remain around input limits (max media duration/size) and failure modes, which would matter for a long-file captioning job.

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%, so the format enum, language code and audio_url are already fully documented in the schema. The description only echoes that output is SRT or VTT and that a language is involved, adding no format defaults, language-code conventions, or constraints on what audio_url may point to.

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?

States a specific verb+resource pair ("Generate SRT/VTT subtitles from audio or video") and immediately names the output format, so the agent knows exactly what it produces. It also distinguishes itself from the transcript siblings by name, so no schema inspection is needed to tell them apart.

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

Usage Guidelines5/5

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

Gives an explicit use case ("Use to caption a video or an audio file") plus an explicit exclusion with named alternatives ("For a plain transcript use stt or transcribe"). Both the when and the when-not are stated, leaving nothing to inference.

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.