Skip to main content
Glama

Parse many media filenames

guessit_batch
Read-onlyIdempotent

Parse up to 1000 filenames in a single call with shared options and get ordered results per input, avoiding repeated parsing requests.

Instructions

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.

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 observedv5.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, closed-world, idempotent behavior, so the safety profile is covered. The description adds real behavioral value beyond that by disclosing per-item partial failure ("{input_string, error}") and that results preserve input order, implying one bad name does not abort the batch.

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?

Three short sentences, front-loaded with the batch scope and cap, followed by the return shape and the comparative rationale. Nothing is wasted or buried.

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?

An output schema exists, yet the description still usefully summarizes the per-entry result/error envelope and ordering guarantee, which is what an agent needs to handle partial failures. The main residual gap is the absence of any hint about what triggers per-item errors or how to handle a fully failed call.

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?

The options parameter is thoroughly documented in the schema, and the description correctly conveys that the same options apply uniformly to every filename. However, the filenames parameter itself is undocumented in the schema (50% coverage) and the description only restates the 1000-item cap already in maxItems, without saying anything about accepted input format.

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?

"Parse up to 1000 filenames in one call with the same options" gives a specific verb (parse), resource (media filenames), and batch scope, and the closing line ("Faster than calling guessit repeatedly") explicitly contrasts it with the single-item sibling guessit.

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?

The description makes the selection condition clear: use this when you have many names and would otherwise loop over guessit. It stops short of stating when not to use it (e.g., a single filename belongs in guessit), so it is strong but not fully explicit about alternatives.

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