Search IMDb titles by query and return normalized result rows from public pages, with an optional limit (default 10, max 20).
IMDb title search. Returns normalized IMDb title search rows from credential-free public IMDb pages. Limit defaults to 10 and clamps to 20.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Rows to return, default 10, max 20 | |
| query | Yes | Search query |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must fully disclose behavior. It mentions 'credential-free' and the limit clamp, but lacks details on response structure, rate limits, or any side effects. Absence of this information creates a significant gap for safe invocation.
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 concise sentences with no extraneous information. The purpose and key constraint are front-loaded, earning their place efficiently.
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?
Despite having only two parameters, the description omits return value structure – 'normalized rows' is vague. No output schema exists, so the description should explain what fields to expect. This gap reduces completeness for an AI agent.
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 coverage is 100% and already documents limit default/max and query. The description repeats the limit clamping, adding minimal extra value beyond the schema. No new parameter semantics are introduced.
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 performs an IMDb title search and returns normalized rows from credential-free public pages. This specific verb-resource combination distinguishes it from other IMDb tools that handle names, awards, or detailed title information.
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?
No guidance is provided on when to use this tool versus alternatives like imdb_title or other search tools. The description only mentions parameter limits, not usage context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.