Skip to main content
Glama

Agent Data Tools: Speech to text and text to speech

Translate subtitles: SRT or VTT into another language, timings kept

subtitles_translate
Read-only

Translate an SRT or WebVTT subtitle file into another language cue by cue, keeping every timing and the file format, so the result drops straight into a video player or editor. Up to 400 cues (40,000 characters) as text or by URL; the source language is detected unless given. Meta M2M100 translation, 100 languages. Use to subtitle videos, courses and podcasts in more languages; pair with transcribe_long, which writes the first SRT. Price $0.02/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "subtitles": "<subtitles>",
      "to": "<to>"
    },
    "name": "subtitles_translate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget language code such as sv, de, es, fr or ja
urlNoURL of an .srt or .vtt file, instead of subtitles
fromNoSource language code (default: detected from the text)
subtitlesYesThe SRT or VTT text (or give url)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses key behavior: up to 400 cues or 40,000 characters, text or URL input, automatic source-language detection, M2M100 translation, 100 languages, and preserved timings and format. It also covers pricing, failed-call behavior, and the fact that repeated calls are charged, which is consistent with readOnlyHint=true and idempotentHint=false.

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?

The description is dense but front-loaded: the core action, format, timing preservation, limits, model, pricing, and usage context all appear without repetition. Every sentence adds practical information for an agent deciding whether and how to call the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still explains what the result is: a translated SRT/VTT that preserves format and timings and can be used directly by a video player or editor. It also gives limits, pricing, and companion-tool context, making the definition complete for correct invocation.

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?

The schema already documents all four parameters at 100% coverage, so the baseline is 3. The description adds useful semantics beyond the schema: input limits, that subtitles can be supplied as text or by URL, and that source language is detected unless explicitly provided.

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?

The description gives a specific verb and resource: translate an SRT or WebVTT subtitle file cue by cue while preserving timings and format. It clearly distinguishes this from generic text translation and names transcribe_long as the companion that produces the initial SRT.

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?

It states when to use the tool: subtitling videos, courses, and podcasts in more languages, and pairing with transcribe_long when an SRT first needs to be created. It does not explicitly say when not to use it versus generic translation tools, so it falls short of a full 5.

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.