Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_episodes

Fetch public IMDb episode rows for a series title, optionally filter by season, and return up to 20 results using a title ID or URL.

Instructions

IMDb title episodes. Returns public IMDb episode rows for a series title. Limit defaults to 10 and clamps to 20. Optional season filters the episodes returned. Pass exactly one of id or url.

Input Schema

NameRequiredDescriptionDefault
idNoIMDb title id
urlNoAbsolute https://www.imdb.com/title/<id>/ URL
limitNoRows to return, default 10, max 20
seasonNoSeason number to request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations, so the description must carry behavioral disclosure. It states the data is public and discloses the limit clamping behavior, but omits authentication needs, rate limits, error handling, and the structure of returned rows. The one-of parameter rule is a useful behavioral constraint.

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?

Four short sentences, front-loaded with the purpose. The opening fragment 'IMDb title episodes.' is slightly redundant with the following sentence, but overall the description is tight and wastes little space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple retrieval tool with no output schema or annotations, the description covers the core purpose and key parameter constraints but lacks details on what an episode row contains and any authentication or rate-limit considerations. Adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds a crucial constraint not in the schema: 'Pass exactly one of id or url.' It also clarifies that season is optional and filters results, and repeats limit defaults. This adds meaningful semantics beyond the schema.

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 ('Returns') and resource ('public IMDb episode rows for a series title'). It distinguishes itself from other IMDb title endpoints by focusing on episode rows, though it does not name a specific sibling alternative. Clear enough for an agent to identify the resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a parameter constraint ('Pass exactly one of id or url') but does not state when to choose this tool over siblings like imdb_title or imdb_title_trivia, nor does it mention prerequisites or exclusions. Usage is implied by the purpose.

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