Skip to main content
Glama

download_subtitle

Download a chosen subtitle from find_subtitles results and load it into the player, saving it beside the video for automatic loading next time. Uses one daily OpenSubtitles download.

Instructions

Download one subtitle chosen from find_subtitles and load it into the player. Saved next to the video when that directory is writable, so it loads automatically next time. Costs one of the user's limited daily OpenSubtitles downloads.

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
fileNoVideo to save the subtitle beside. Defaults to the playing file.
loadNoLoad it into the player after downloading (default true)
file_idYesThe file_id from a find_subtitles result
languageNoLanguage code of the chosen subtitle, used in the saved filename

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does well on side effects: it writes beside the video when the directory is writable so the file loads next time, and it consumes a metered daily download allowance. It says nothing about what happens when the directory is not writable (fallback location? error?), whether an existing subtitle is overwritten, or whether the quota is decremented on failure.

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 short sentences, front-loaded with the action and then the consequences (persistence and quota cost). Every clause carries information; nothing is redundant.

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 4-parameter, no-output-schema mutation the description covers purpose, persistence behaviour, and quota cost, which is most of what an agent needs. The remaining gap is failure behaviour when the target directory is read-only and whether the download is repeatable without extra cost.

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?

Schema coverage is 100%, so all four parameters are already documented, including defaults for file and load. The description adds workflow meaning by anchoring file_id to a find_subtitles result, but adds no syntax or format detail beyond the schema.

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 concrete verb and resource ("Download one subtitle ... and load it into the player") and ties the input to a find_subtitles result, which separates it from the search sibling. It does not explicitly contrast with load_subtitle, so an agent must infer the division of labour.

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?

Clear context: use it after find_subtitles has produced a file_id, and it names a real cost constraint ("one of the user's limited daily OpenSubtitles downloads") that tells the agent to be sparing. No explicit when-not-to-use or alternative path (e.g. an existing local subtitle) is given.

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

Deploy Server

Other Tools