Crawlora MCP

tmdb_tv_list

Read-only

Fetch TMDB TV charts or filtered TV discovery results, with page and continuation metadata. Use tmdb_search to find a title, tmdb_movie_list for films, or tmdb_tv for one show's details.

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": "tmdb_tv_list"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based page, default 1.
`limit`	No	Max shows, default 10, max 20.
`date_to`	No	Release/first-air date upper bound, YYYY-MM-DD.
`sort_by`	No	Sort order; allowed values depend on movie vs TV.
`category`	No	TV chart, default popular.
`date_from`	No	Release/first-air date lower bound, YYYY-MM-DD.
`min_votes`	No	Minimum vote count.
`max_rating`	No	Maximum TMDB user rating, 0-10.
`min_rating`	No	Minimum TMDB user rating, 0-10.
`max_runtime`	No	Maximum runtime in minutes.
`min_runtime`	No	Minimum runtime in minutes.
`with_genres`	No	Comma- or pipe-separated TMDB genre ids.
`include_adult`	No	Include adult titles.
`original_language`	No	Two-letter original-language code.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that — pagination and continuation metadata are returned — but says nothing about rate limits, default result size, or how chart mode interacts with the filter parameters. With annotations carrying the safety burden, a 3 is appropriate.

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?

Two sentences: the first states what it returns, the second routes the agent away from the three nearest siblings. Nothing is wasted and the capability statement is front-loaded before the disambiguation.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and all 14 parameters are documented in the schema. The one residual gap is that the description never explains the dual mode — chart browsing versus filtered discovery — specifically how category relates to the rating/runtime/genre filters, which is the main thing an agent could get wrong when calling this tool.

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% across all 14 parameters, so the schema itself documents page, limit, date bounds, sort_by, ratings, runtime and genres. The description only echoes the page/continuation concept and does not clarify semantics the schema leaves implicit, such as how category (chart mode) interacts with the discovery filters. Baseline 3 is correct.

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

Purpose5/5

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

The description names a specific verb (Fetch) and resource (TMDB TV charts / filtered TV discovery results) and explicitly differentiates itself from three named siblings: tmdb_search (title lookup), tmdb_movie_list (films), and tmdb_tv (single show details). An agent can select this tool without opening any schema.

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

Usage Guidelines5/5

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

It names the alternatives and the condition that selects each: search for a title, movie_list for films, tv for one show's details — leaving this tool for charts and filtered discovery. This is explicit when-to-use and when-not-to-use routing, not implied context.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.