Fetch a TMDB collection by ID to retrieve its overview and member movies for franchise grouping, using credential-free public data.
Get a TMDB collection. Returns a normalized TMDB collection (franchise grouping), including its overview and server-rendered member movies. Credential-free public TMDB data.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | TMDB collection id or id-slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It discloses that the data is credential-free public TMDB data and that the response includes a normalized collection with overview and server-rendered member movies. This goes beyond a generic 'get' description, though it does not cover output structure or error behavior.
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?
The description is two concise sentences with no fluff or redundancy. The main action is front-loaded, followed by useful return details and access constraints. Every clause contributes value.
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 single-parameter tool with no output schema, the description provides enough context to understand the resource, the return contents, and the auth-free nature. Minor details such as the exact shape of the normalized response are not specified, but they are not necessary for an agent to select and invoke this tool correctly.
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?
The input schema already fully describes the only parameter as 'TMDB collection id or id-slug,' so schema coverage is 100%. The description adds no additional parameter-level meaning beyond confirming the resource type. A baseline score of 3 is appropriate because the schema carries the semantic weight.
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 a specific verb and resource: 'Get a TMDB collection.' It further clarifies that a collection is a franchise grouping with overview and member movies, which distinguishes it from sibling tools like tmdb_movie, tmdb_tv, and tmdb_person. The purpose is unambiguous and actionable.
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?
The description implies when to use the tool: when you need a TMDB collection or franchise grouping. It does not explicitly name alternatives or state when not to use it, though 'franchise grouping' and 'member movies' provide contextual cues. This is adequate but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.