Skip to main content
Glama

Parse a media filename

guessit
Read-onlyIdempotent

Parse movie or TV filenames and release names into structured metadata including title, year, season, episode, codecs, language, and release group. Accepts file names or full paths.

Instructions

Extract metadata from one movie or TV episode filename or release name: title, year, season, episode, episode_title, screen_size, source, video_codec, audio_codec, language, subtitle_language, release_group, streaming_service, container, type (movie or episode) and more (56 properties). Output matches Python guessit's JSON. Pass just the file name or a full path; directory names help (e.g. "Show/Season 2/episode.mkv").

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": "guessit"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoOptional guessit options, as in the library and Python guessit: type ("movie" | "episode"), output ("python" default: language/country as names like "French"; "codes": {"alpha3": "fra"} objects that keep regions such as pt-BR), expected_title, allowed_languages, allowed_countries, name_only, date_day_first, date_year_first, excludes, includes.
filenameYesFilename, path or release name, e.g. "The.Matrix.1999.1080p.BluRay.x264-GRP.mkv"

Output Schema

NameRequiredDescriptionDefault
typeNo
yearNo
titleNo
seasonNo
episodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and determinism are covered structurally. The description adds the useful compatibility note that output matches Python guessit's JSON and that 56 properties may be present, but says nothing about parsing ambiguity, failure behavior, or unknown-field handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core verb and resource, then field list, then invocation hint—logical ordering with little waste. The '(56 properties)' parenthetical and 'and more' phrasing are slightly loose but not distracting.

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 present and annotations covering the safety profile, the description need not explain return structure, and it doesn't over-explain. It covers input shape, option passthrough, and output compatibility, leaving only sibling routing unaddressed.

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 nested options object (type, output, expected_title, allowed_languages, etc.) is already well documented in the schema; the baseline of 3 applies. The description adds marginal value by clarifying that filenames can be bare names, full paths, or release names and that directory context is used.

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 specific verb and resource ('Extract metadata from one movie or TV episode filename or release name') and enumerates the returned fields, so an agent knows exactly what comes back. The word 'one' implicitly separates it from guessit_batch, but no sibling is named explicitly, leaving that distinction to inference.

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?

Gives concrete invocation context: pass just the file name or a full path, and directory names in the path improve parsing (with an example). It does not state when to prefer guessit_batch or guessit_properties, so the alternative-selection guidance is incomplete.

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