Skip to main content
Glama

OpenSubtitles

Parse a video filename

guess_filename
Read-onlyIdempotent

Parse a movie or episode filename with guessit-js (title, year, season, episode, release group, resolution, source, codec). Offline and free; use it to build a precise search_subtitles call, or pass the filename to search_subtitles directly.

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": {
      "filename": "<filename>"
    },
    "name": "guess_filename"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYese.g. "The.Matrix.1999.1080p.BluRay.x264-GROUP.mkv"

Output Schema

NameRequiredDescriptionDefault
rawYesFull guessit-js result
typeYes
yearYes
titleYes
seasonYes
sourceYes
episodeYes
containerYes
screen_sizeYes
video_codecYes
release_nameYesThe filename without directory and extension, used to rank subtitle releases
episode_titleYes
release_groupYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the parse is offline and free, and that the extracted metadata is intended to feed search_subtitles, which is useful workflow context. It does not describe latency, failure behavior, or what happens on an unparseable filename, but with the output schema present that gap is minor.

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 purpose and extracted-field list come first, and the actionable routing advice to search_subtitles follows immediately, so the most decision-relevant content is front-loaded.

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?

For a one-parameter, read-only parsing utility with an output schema, the definition supplies everything needed: what it parses, that it is offline/free, and how its result feeds the next tool. No authentication, side effects, or return-format explanation is required beyond this.

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 100% and the single filename parameter already carries a realistic example in the schema. The description implies the input is a raw release-style filename but adds no format rules, length constraints, or guidance on what an unparseable input yields. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb and resource ('Parse a movie or episode filename with guessit-js') and enumerates what the parse yields (title, year, season, episode, release group, resolution, source, codec). That enumeration distinguishes it from siblings like search_subtitles and get_subtitle_details, which operate on subtitles rather than raw filenames.

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?

It gives an explicit when: 'use it to build a precise search_subtitles call,' and names the alternative path: 'or pass the filename to search_subtitles directly.' The agent can decide between precision and skipping this step without opening any schema.

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.