Skip to main content
Glama

Convert an SRT or WebVTT file to another language

translate_subtitles
Read-only

Translate an SRT or WebVTT subtitle file into another language. Only the cue text is translated; every cue number, timing line and header is copied exactly, and the output is checked to parse back to the same cues and timings, or it is refused unpaid. Body { subtitles, to, from }: up to 50 KB. Workers AI (Llama 3.1 8B) translates the text, so check it before publishing. Related tools on this server, for a different need: translate when you need to translate text between languages. Price: $0.004 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
toYesTarget language name or code, e.g. German or de
fromNoSource language, optional; detected by the model when not given
subtitlesYesThe SRT or WebVTT text, up to 50 KB (JSON body field)

Output Schema

NameRequiredDescriptionDefault
toNo
cuesNo
fromNo
modelNo
formatNo
sourceNo
checkedAtNo
subtitlesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld; the description goes well beyond them by disclosing the exact preservation contract (cue numbers, timing lines, headers copied), an output self-check that refuses rather than returns corrupt files, the underlying model (Llama 3.1 8B), the payload ceiling, and the billing rule that failed calls are not charged. The pricing and x402 payment requirement are operationally important facts an agent cannot infer from structured fields.

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-loads purpose and the preservation guarantee, then moves to limits, model quality, alternatives and price in a logical order. It is dense but nearly every clause carries decision-relevant information; the bracketed 'Body { subtitles, to, from }' reshuffling of the schema is the one mildly redundant element.

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?

An output schema exists, so return-value explanation is unnecessary, and the description instead covers everything an agent still needs: payload limit, language detection, fidelity guarantee with failure semantics, model quality warning, cost and payment rail. Nothing material for correct invocation is missing.

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%, with 'to' and 'from' already carrying examples and the auto-detection behavior, so the baseline applies. The description's parameter section ('Body { subtitles, to, from }: up to 50 KB') largely restates the schema and adds only the size limit, which is already on the subtitles field.

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 and resource ('Translate an SRT or WebVTT subtitle file into another language') and immediately bounds the transformation to cue text only, which is exactly what separates it from the generic 'translate' sibling. An agent knows from the first sentence what it gets back: same cues and timings, different language.

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?

Explicitly routes the agent: use this for subtitle files, and 'translate when you need to translate text between languages' for plain text. It also supplies the practical selection condition of a 50 KB body limit and a quality caveat ('check it before publishing'), so the agent can decide both whether and how to use it.

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.

Resources