Skip to main content
Glama

guessit-js

Parse many media filenames

guessit_batch
Read-onlyIdempotent

Parse up to 100 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.

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": {
      "filenames": "<filenames>"
    },
    "name": "guessit_batch"
  }
}

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.
filenamesYes

Output Schema

NameRequiredDescriptionDefault
resultsYesOne entry per input name, in order

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 the safety profile is covered. The description adds genuine value beyond that by disclosing per-item partial failure semantics and result ordering, though it does not say whether exceeding 100 is an error or a truncation. With annotations carrying most of the burden, a 3 is fair.

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 with no filler: the capability and limit come first, then the return shape, then the performance rationale. Every clause carries information an agent would otherwise have to infer.

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?

Covers the batch cap, uniform option application, ordering, and per-item error handling, which is enough for an agent to call it confidently; an output schema exists so return structure need not be elaborated further. The only gap is behavior at or above the 100-item boundary.

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 50%, and the options object already carries a detailed inline description of every supported guessit option. The description contributes only the notion that the same options apply uniformly to all filenames and restates the 100-item cap, which is already encoded as maxItems in the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource (parse filenames) plus the batch scope (up to 100 per call, shared options). The closing comparison to calling guessit repeatedly implicitly distinguishes it from the single-input sibling, so an agent can pick correctly without opening a schema.

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 a clear usage context: use this when you have many filenames because it is faster than repeated single calls. It does not state exclusions (e.g., what to do beyond 100 names, or when a single guessit call is preferable), so it falls short of explicit when-not guidance.

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.