Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_credits

Fetch full cast and crew lists for an IMDb title in named sections. Provide a title ID or URL to get names, roles, and characters.

Instructions

IMDb title credits. Returns the full cast and crew IMDb lists for a title, in named sections. Pass exactly one of id or url. Each credit has a name, IMDb name URL, role and, for cast, the character. The cast returns up to 2,000 rows and other sections up to 100.

Input Schema

NameRequiredDescriptionDefault
idNoIMDb title id
urlNoAbsolute https://www.imdb.com/title/<id>/ URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful behavioral traits: the returned sections, per-credit fields (name, name URL, role, character for cast), and result caps (2,000 cast rows, 100 for other sections). It omits any auth, error, or pagination-beyond-limit behavior, but the structural and volume disclosure is solid.

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?

Four short sentences, each carrying distinct information: purpose, input constraint, return shape, and result limits. Purpose is front-loaded and there is no filler or redundancy.

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?

For a read tool with no output schema and no annotations, the description supplies the essential return shape, section structure, and row limits. It could still clarify how an id is obtained or whether sections are returned selectively, but nothing critical to correct invocation is missing.

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 the baseline is 3 and the id/url meanings are already documented. The description adds a genuine constraint not expressible in the schema: the two inputs are mutually exclusive ('pass exactly one'), which is valuable since the schema marks both as optional with an empty required list.

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?

The description gives a specific verb+resource: it returns the full cast and crew IMDb lists for a title, and notes the result is organized in named sections. The 'for a title' scope implicitly separates it from imdb_name_credits and imdb_title_company_credits, but it never names an alternative explicitly, so differentiation requires inference.

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?

There is no explicit when-to-use or when-not-to-use guidance relative to siblings like imdb_title, imdb_name_credits, or imdb_title_company_credits. Usage is only implied by the fact that the tool returns cast/crew for a title. The 'exactly one of id or url' rule is a parameter constraint rather than tool-selection guidance.

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