Fetch IMDb title user reviews as normalized JSON rows. Specify an IMDb title ID or URL to retrieve up to 20 reviews, defaulting to 10.
IMDb title user reviews. Returns normalized public IMDb user review rows. Limit defaults to 10 and clamps to 20. 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 | |
| limit | No | Rows to return, default 10, max 20 |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries the burden. It mentions normalization, limit defaults and clamping, but lacks details on pagination, rate limits, or auth requirements.
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?
Three concise sentences: purpose, output description, usage rule. No wasted words.
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?
Adequately covers key aspects for a simple review list tool given no output schema, but could mention return fields or ordering.
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 covers 100% of parameters, but description adds the crucial constraint 'Pass exactly one of id or url', which is not reflected in schema's optional fields.
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?
Clearly states it returns IMDb title user reviews as normalized rows. Distinguishes from sibling tools like imdb_title or imdb_title_credits by focusing on reviews.
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?
Provides explicit instruction to pass exactly one of id or url, but does not contrast with sibling tools or specify when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.