Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_name_credits

Fetch a person's IMDb filmography by IMDb name ID or profile URL, grouped into Actor, Director, and Self credits with title, year, role, and episode count.

Instructions

IMDb name credits. Returns a person's IMDb filmography, grouped into sections such as Actor, Director and Self. Pass exactly one of id or url. Each credit has its title, year, role and episode count. A section returns up to 100 credits, so total can exceed the rows returned.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.8/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 real work: it discloses the section-grouping behavior, the fields per credit (title, year, role, episode count), and a concrete pagination constraint (100 credits per section, so `total` can exceed returned rows). It stops short of stating permissions, error behavior, or whether id/url are interchangeable beyond the exclusivity rule.

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?

Five short sentences, each carrying distinct information: purpose, output shape, input rule, credit fields, and pagination caveat. Front-loaded with the core purpose and no redundant restating of the tool name.

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?

With no output schema and no annotations, the description supplies the return shape (sections, per-credit fields), the input exclusivity rule, and the pagination cap. An agent can call this correctly, though a note on invalid-id handling would close the remaining gap.

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 parameter meanings are already documented; baseline would be 3. The description adds a genuine constraint beyond the schema — 'Pass exactly one of `id` or `url`' — which encodes a mutual-exclusivity rule the flat properties list cannot express.

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 and resource ('Returns a person's IMDb filmography') and adds the distinguishing detail that results are grouped into sections like Actor, Director and Self. This separates it from imdb_name (profile) and imdb_name_awards, though it does not name those siblings explicitly.

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?

The description implies when to use it (you want a person's filmography rather than their bio or awards), but never states when-not or names an alternative tool. Usage is left to inference from the described output.

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