Retrieve all TMDB movie and TV genre IDs for browse pages. Use movie values with movie list filters and TV values with TV list filters.
List TMDB browse genres. Returns every genre ID for TMDB movie and TV browse pages. Use movie values only with movie list filters and TV values only with TV list filters.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 full behavioral burden. It discloses that this is a read-only enumeration of all genres and enforces a movie-vs-TV value separation constraint, which is useful. It stops short of stating auth needs, pagination, or rate limits, leaving gaps for a no-annotation tool.
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 sentences, front-loaded with the purpose and return value before the usage constraint. No filler, though the second and third sentences overlap somewhat in scope.
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?
With no output schema, the description steps in to summarize the return (all movie and TV genre IDs) and the constraint on consuming them. For a zero-parameter lookup tool this is largely complete, missing only explicit routing to the sibling list tools.
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 tool takes zero parameters, so there is nothing for the description to document beyond what the empty schema already shows. Baseline 4 applies; no parameter meaning is required or missing.
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?
States a specific verb and resource ("List TMDB browse genres") and clarifies the return payload ("every genre ID for TMDB movie and TV browse pages"). It is clearly distinguishable from browsing siblings, though it does not name tmdb_movie_list/tmdb_tv_list explicitly.
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?
Offers contextual guidance on how to apply the results ("movie values only with movie list filters and TV values only with TV list filters"), which implies pairing with the list tools. However, it never explicitly states when to call this tool versus tmdb_movie_list or tmdb_tv_list; usage is inferred rather than declared.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.