guessit-js
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
guessit-js extracts metadata (title, year, season, episode, resolution, codecs, languages, release group, ...) from movie and TV filenames. Use guessit for one name, guessit_batch for many. Output matches Python guessit; pass options.output="codes" for ISO language codes with regions.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| guessitA | 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"). |
| guessit_batchA | Parse up to 1000 filenames in one call with the same options. Returns one entry per name, in order: {input_string, result} or {input_string, error}. Faster than calling guessit repeatedly. |
| guessit_propertiesA | List every property guessit can return with its possible values (enum values such as source: ["Blu-ray", "Web", ...]; [null] for free-form ones such as title). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have clearly distinct roles: single-filename parsing, bulk parsing, and schema/introspection. An agent can trivially choose between guessit and guessit_batch based on input volume, and guessit_properties is unmistakably a metadata-listing tool.
All names are snake_case and share a predictable 'guessit_' prefix family, so the grouping is obvious. The only minor deviation is that the base parsing tool is just 'guessit' with no action suffix while its siblings carry one.
Three tools is well-scoped for a focused filename-parsing library: one core operation, one performance variant, and one introspection helper. No tool feels redundant or padding.
Core parsing, batch parsing, and property enumeration cover the main workflows end to end. A minor gap is that no tool exposes the available parsing options (e.g. type, includes/excludes) even though guessit_batch refers to 'the same options'.