Retrieve a page of TMDB's popular people, including IDs, names, known-for titles, profile images, and detail URLs for building people directories.
List popular people on TMDB. Returns one page from TMDB's Popular People directory, including each person's id, name, known-for titles, profile image, and detail URL.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page, default 1 | |
| limit | No | Max people, default 10, max 20 |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. It usefully discloses that results come one page at a time from TMDB's Popular People directory and names the returned fields, but it does not mention authentication, rate limits, or pagination beyond the single-page statement.
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 short sentences, zero waste, and the core operation is front-loaded. The second sentence efficiently explains pagination and the main returned fields.
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?
There is no output schema, but the description names the key returned fields and explains the one-page nature of the result. Combined with fully documented parameters, this is nearly complete for a simple popular-people listing tool, though it could say more about result ordering or source constraints.
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 both page and limit documented directly in the input schema. The description says 'one page' but adds no syntax or format details beyond the schema, so the baseline 3 is appropriate.
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 states a specific action and resource: listing popular people on TMDB. It clearly implies a browse/list operation rather than detail lookup, though it does not explicitly distinguish itself from siblings like tmdb_person or tmdb_search.
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?
Usage is implied by 'popular people' and the Popular People directory, so an agent can infer this is for browsing popular personalities. However, there is no explicit guidance on when to use this versus tmdb_search, tmdb_person, or other TMDB list tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.