TMDB MCP Server

Popular TV Shows

tv_popular

Retrieve popular TV shows from The Movie Database (TMDB) API. Use this tool to access trending television series lists with pagination support.

Instructions

Get popular TV shows

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tv_popular"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number (1-1000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Apr 21, 2026

TDQS

C2.7/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 the full burden of behavioral disclosure. It only states the action ('Get') without details on permissions, rate limits, pagination, or response format. For a tool with no annotations, this is a significant gap in transparency.

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 extremely concise at three words, with no wasted language. It's front-loaded and efficiently conveys the core purpose, though this brevity contributes to gaps in other dimensions.

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 the complexity of a TV data tool with no annotations, no output schema, and many sibling tools, the description is incomplete. It lacks details on behavior, usage context, and output, making it insufficient for an agent to fully understand how to invoke it effectively.

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?

The input schema has 100% description coverage, with the 'page' parameter fully documented. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating value.

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

Purpose3/5

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

The description 'Get popular TV shows' states the basic purpose with a verb ('Get') and resource ('popular TV shows'), but it's vague about what 'popular' means (e.g., by what metric or time frame) and doesn't distinguish it from similar sibling tools like 'tv_top_rated' or 'trending_tv_week'. It's adequate but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools for TV content (e.g., 'tv_top_rated', 'trending_tv_week'), the description doesn't indicate context, exclusions, or comparisons, leaving the agent to infer usage based on tool names alone.

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