Skip to main content
Glama

OpenSubtitles

Download subtitle

download_subtitle

Download one subtitle file by file_id and return its text (or a temporary link), with optional format conversion, FPS conversion or time shift. Each call uses one download from the user's daily OpenSubtitles quota, so pick the file with search_subtitles first; the result reports the remaining quota.

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": {
      "file_id": "<file_id>"
    },
    "name": "download_subtitle"
  }
}

Input Schema

NameRequiredDescriptionDefault
in_fpsNoFrame rate the subtitle was timed for (use with out_fps)
file_idYesfile_id from search_subtitles or get_subtitle_details
out_fpsNoFrame rate of your video (use with in_fps)
deliveryNocontent = return the subtitle text; link = return only a temporary download URL (for large files or saving to disk)content
timeshiftNoShift all cues by this many seconds, e.g. 2.5 or -1
sub_formatNoConvert to this format. Omit to keep the original (usually srt).

Output Schema

NameRequiredDescriptionDefault
linkYesTemporary download URL (valid for a few hours)
quotaYes
formatYes
contentYesSubtitle text (delivery=content)
file_idYes
file_nameYes
mime_typeYes
truncatedYes
size_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the two facts an agent most needs: each call burns a daily quota unit, and the response reports the remaining quota — which explains the non-idempotent, non-read-only hints. It does not cover failure behavior (e.g. exhausted quota) or whether link URLs expire, so it stops short of full transparency.

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?

Two sentences, front-loaded with the core action and followed by the cost/ordering constraint. No filler and nothing an agent must read past to find the essential guidance.

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 full schema coverage, annotations, and an output schema, the description only needed to supply the non-structured essentials — quota cost and the search-first ordering — and it does both.

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 schema already documents file_id, in_fps/out_fps pairing, timeshift, delivery and sub_format. The description only restates the optional conversions at a high level, adding no syntax or format nuance beyond the schema — the baseline 3 case.

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 names a specific verb and resource ('Download one subtitle file by file_id') and enumerates its capabilities (text or temporary link, format/FPS conversion, time shift). An agent can distinguish it immediately from search_subtitles or get_subtitle_details.

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 gives explicit prerequisite guidance ('pick the file with search_subtitles first') and surfaces the cost condition ('one download from the user's daily OpenSubtitles quota'). What's missing is any when-not guidance, such as what to do if quota is exhausted or when get_subtitle_details alone suffices.

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.