Skip to main content
Glama

OpenSubtitles

Subtitle details

get_subtitle_details
Read-onlyIdempotent

Full metadata for one subtitle from a search result: all files (multi-CD), uploader, comments, links, and related subtitles for the same title and language. Does not use download 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": {
      "subtitle_id": "<subtitle_id>",
      "feature_id": "<feature_id>"
    },
    "name": "get_subtitle_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoThe subtitle's language (speeds up the lookup)
feature_idYesfeature.feature_id of the same search result
subtitle_idYessubtitle_id from search_subtitles
related_limitNo

Output Schema

NameRequiredDescriptionDefault
relatedYesOther subtitles for the same title and language, most similar release first
subtitleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds useful behavior beyond annotations by saying it returns full metadata and does not consume download quota, though it does not discuss rate limits or other operational constraints.

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 front-loaded and tightly structured: it names the object, enumerates the returned metadata, then adds the quota behavior. Every sentence adds useful information without repetition.

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?

With an output schema and rich annotations already present, the description provides enough context for an agent to understand the tool's return contents and quota behavior. The main gap is that usage guidance relative to siblings and related_limit semantics are not fully elaborated.

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 coverage is 75%, and the schema already explains subtitle_id, feature_id, and language. The description reinforces that the subtitle comes from a search result and that related results are for the same title and language, but it does not clarify related_limit, which is the one parameter lacking schema description.

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 states a specific resource and scope: full metadata for one subtitle from a search result, including files, uploader, comments, links, and related subtitles. It also distinguishes itself from the download path by explicitly noting that it does not use download quota.

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

Usage Guidelines3/5

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

The description implies this tool is used after a search result and is not for downloading the file, but it does not explicitly name alternatives such as download_subtitle or state when not to use this tool. The guidance is present but indirect.

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.