Fetch normalized IMDb technical specifications—runtime, sound mix, color, aspect ratio—by passing exactly one IMDb title ID or URL.
IMDb title technical specs. Returns normalized public IMDb technical specifications such as runtime, sound mix, color, and aspect ratio. Pass exactly one of id or url.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | IMDb title id | |
| url | No | Absolute https://www.imdb.com/title/<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 are provided, so the description carries the full burden. It states it returns 'normalized public IMDb technical specifications', implying read-only and public access, but does not disclose rate limits, authentication needs, or error behavior. Adequate for a simple retrieval tool but could be more transparent.
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, front-loaded with purpose and followed by usage instruction. Every sentence is necessary and no filler. Excellent conciseness.
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?
For a simple retrieval tool with two parameters and no output schema, the description covers the key aspects: what it returns (list of specs), how to call it (pass one identifier), and the data source (IMDb title). It could mention that the output is a JSON object to increase completeness, but overall sufficient.
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 description coverage is 100%, with 'id' and 'url' already described. The description adds value by clarifying that exactly one parameter must be passed, which is not obvious from the schema (neither is required). This guidance enhances usability.
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?
The description clearly states the tool returns IMDb technical specifications such as runtime, sound mix, color, and aspect ratio. It distinguishes itself from sibling tools like imdb_title or imdb_title_awards by focusing on technical specs.
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?
Explicitly says 'Pass exactly one of `id` or `url`', providing a clear usage constraint. However, it does not elaborate on when to use this tool versus alternatives beyond the implicit purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.