Fetch normalized public IMDb person metadata and known-for rows by passing exactly one IMDb name ID or profile URL. Get clean JSON for cast and crew research.
IMDb name detail. Returns normalized public IMDb person metadata and known-for rows. Pass exactly one of id or url.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | IMDb name id | |
| url | No | Absolute https://www.imdb.com/name/<id>/ URL |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description mentions it returns 'normalized public' data and 'known-for rows' but omits error handling, authentication, or rate limits. Adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no fluff, front-loaded with purpose. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Two parameters, no output schema; description covers input constraint and output content. Lacks return format details, but sufficient for a simple retrieval tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% coverage with basic descriptions; description adds the critical constraint 'Pass exactly one of id or url', which is not in schema, providing significant added value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States it returns 'IMDb person metadata and known-for rows', which is specific and distinct from sibling tools like imdb_name_awards or imdb_name_credits.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Specifies 'Pass exactly one of id or url', which clarifies parameter usage but does not compare to alternatives or state when to use this tool versus other imdb_name_* tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.