tmdb_search_tv
Search for TV shows on TMDB by query. Returns paginated search results with series metadata.
Instructions
Search for TV shows on TMDB.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| page | No | ||
| api_key | No |
Search for TV shows on TMDB by query. Returns paginated search results with series metadata.
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 annotations provided. The description lacks details on authentication, rate limits, pagination, or return format. It merely restates the basic function.
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 and to the point, containing only necessary words. However, it could be expanded to include critical context.
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?
Given the lack of annotations, output schema, and parameter descriptions, the description fails to provide enough context for proper tool usage. The agent would be left with many unanswered questions.
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% for 3 parameters. The description adds no meaning to parameters like 'page' or 'api_key' beyond their names.
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 action (search) and resource (TV shows) on TMDB. However, it does not differentiate from sibling tools like tmdb_search_movies or tmdb_popular_tv, leaving ambiguity about which tool to use.
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 on when to use this tool versus the several other TV search tools (e.g., tmdb_tv, tmdb_popular_tv). The agent has no context for selection.
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