TMDB MCP Server

Search TV Shows

search_tv

Find TV shows by entering search terms to access comprehensive information from The Movie Database (TMDB).

Instructions

Search for TV shows by query

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_tv"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Search query
`page`	No	Page number (1-1000)
`include_adult`	No	Include adult content

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Apr 21, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions searching by query but doesn't disclose behavioral traits such as pagination behavior (implied by 'page' parameter), rate limits, authentication needs, result format, or whether it's a read-only operation. This leaves significant gaps for an agent to understand how to use it effectively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple search tool, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain return values, usage context, or behavioral constraints, leaving the agent with insufficient information to operate the tool effectively in a complex environment.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents parameters (query, page, include_adult). The description adds no additional meaning beyond implying a search query, which is already covered. Baseline score of 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Search for') and resource ('TV shows'), making the purpose immediately understandable. It distinguishes from general search tools like 'search_multi' by specifying TV shows, though it doesn't explicitly differentiate from 'search_movie' or other media-specific searches beyond the title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'search_movie', 'search_person', 'search_multi', and various TV-specific tools (e.g., 'tv_popular', 'tv_details'), there's no indication of when a search is preferred over browsing or filtering by other criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.