Skip to main content
Glama

OpenSubtitles

Find movies and TV shows

search_features
Read-onlyIdempotent

Look up movies, TV shows and episodes on OpenSubtitles (title, year, IMDb/TMDB/feature ids, seasons and episode counts, subtitle counts per language). Use it to disambiguate a title before search_subtitles, or to find a show's seasons and episodes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoall
yearNo
limitNo
queryNoTitle, e.g. "Chicago Fire"
imdb_idNo
tmdb_idNo
feature_idNo
include_episodesNoList every episode (title, feature_id, IMDb id) per season for TV shows

Output Schema

NameRequiredDescriptionDefault
totalYes
featuresYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that results include per-language subtitle counts, which tells the agent something about the payload beyond a bare search. It says nothing about rate limits, authentication, pagination via the limit parameter, or what happens when an id and a query are supplied together.

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, no filler: the capability and its returned fields come first, and the usage routing follows immediately. Every clause carries information an agent needs for selection.

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

Completeness3/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 values need not be spelled out, and the annotations cover the safety traits. However, for an 8-parameter tool with 25% schema coverage, the description leaves the type filter, the limit default/cap, and the query-vs-id precedence unexplained.

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?

With only 25% schema description coverage across 8 parameters, the description partially compensates by naming the id flavors (IMDb/TMDB/feature ids) and the year/season/episode aspects. The type enum values, the limit semantics, and how query interacts with the id parameters remain undocumented in both places.

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?

A specific verb ("Look up") plus a specific resource set ("movies, TV shows and episodes on OpenSubtitles"), and it enumerates the fields the lookup returns (title, year, IMDb/TMDB/feature ids, season and episode counts, subtitle counts). It is clearly distinguishable from search_subtitles, which returns subtitles rather than title metadata.

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 names an alternative and the condition that selects it: "disambiguate a title before search_subtitles", plus a second use case (finding a show's seasons and episodes). There is no explicit when-not guidance (e.g. what to do if you already hold a feature_id), but the routing intent is unambiguous.

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.