tmdb_search_tv
Search TMDB for TV shows using a query string; supports pagination to browse results.
Instructions
Search for TV shows on TMDB.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| page | No | ||
| api_key | No |
Search TMDB for TV shows using a query string; supports pagination to browse results.
Search for TV shows on TMDB.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| page | No | ||
| api_key | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No behavioral traits are disclosed beyond the bare action. No annotations are provided, and the description lacks details on rate limits, pagination, or error handling.
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 very short but under-specified. It could be concise yet include essential details like query requirements or results format.
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?
Without output schema, annotations, or parameter explanations, the description is insufficient for an agent to use the tool correctly in diverse scenarios.
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 0%. The description does not explain the purpose or format of any parameters, leaving the agent to infer from names alone.
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 searches for TV shows on TMDB, with a specific verb and resource. However, it does not differentiate itself from sibling tools like tmdb_popular_tv or tmdb_tv.
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 over alternatives, such as tmdb_popular_tv for trending shows or tmdb_tv for specific TV show details.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'
If you have feedback or need assistance with the MCP directory API, please join our Discord server