Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

tmdb_tv_list

Fetch TMDB TV show charts by category, then filter by genre, language, air date, rating, votes, or runtime to retrieve ranked TV lists.

Instructions

Get a TMDB TV chart. Returns a page of TMDB TV shows from the category chart (popular by default, or top_rated, airing_today, on_the_air), optionally refined by sort_by, with_genres, original_language, first-air-date bounds date_from and date_to, rating, votes and runtime. limit defaults to 10 (max 20). A filtered page with no matches returns an empty shows array.

Input Schema

Name	Required	Description
`page`	No	1-based page, default 1
`limit`	No	Max shows, default 10, max 20
`date_to`	No	First-air date upper bound (YYYY-MM-DD)
`sort_by`	No	Sort order
`category`	No	TV chart, default popular
`date_from`	No	First-air date lower bound (YYYY-MM-DD)
`min_votes`	No	Minimum vote count
`max_rating`	No	Maximum rating, 0-10
`min_rating`	No	Minimum rating, 0-10
`max_runtime`	No	Maximum runtime in minutes
`min_runtime`	No	Minimum runtime in minutes
`with_genres`	No	Comma- or pipe-separated TV genre ids: 10759,16,35,80,99,18,10751,10762,9648,10763,10764,10765,10766,10767,10768,37
`include_adult`	No	Include adult titles
`original_language`	No	Two-letter original-language code

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.17.5Sep 26, 2026

addedInput schema / properties / category / enum

Added value: +[
+  "popular",
+  "top_rated",
+  "airing_today",
+  "on_the_air"
+]

addedInput schema / properties / sort_by / enum

Added value: +[
+  "popularity.desc",
+  "popularity.asc",
+  "vote_average.desc",
+  "vote_average.asc",
+  "first_air_date.desc",
+  "first_air_date.asc",
+  "name.asc",
+  "name.desc"
+]

changedInput schema / properties / with_genres / description

Previous value: -"Comma- or pipe-separated TMDB genre ids"New value: +"Comma- or pipe-separated TV genre ids: 10759,16,35,80,99,18,10751,10762,9648,10763,10764,10765,10766,10767,10768,37"

Changed12 schema fields changedAug 4, 2026

addedInput schema / properties / date_from

Added value: +{
+  "description": "First-air date lower bound (YYYY-MM-DD)",
+  "type": "string"
+}

addedInput schema / properties / date_to

Added value: +{
+  "description": "First-air date upper bound (YYYY-MM-DD)",
+  "type": "string"
+}

addedInput schema / properties / include_adult

Added value: +{
+  "description": "Include adult titles",
+  "type": "boolean"
+}

addedInput schema / properties / max_rating

Added value: +{
+  "description": "Maximum rating, 0-10",
+  "type": "number"
+}

addedInput schema / properties / max_runtime

Added value: +{
+  "description": "Maximum runtime in minutes",
+  "type": "integer"
+}

addedInput schema / properties / min_rating

Added value: +{
+  "description": "Minimum rating, 0-10",
+  "type": "number"
+}

addedInput schema / properties / min_runtime

Added value: +{
+  "description": "Minimum runtime in minutes",
+  "type": "integer"
+}

addedInput schema / properties / min_votes

Added value: +{
+  "description": "Minimum vote count",
+  "type": "integer"
+}

addedInput schema / properties / original_language

Added value: +{
+  "description": "Two-letter original-language code",
+  "type": "string"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "1-based page, default 1",
+  "type": "integer"
+}

addedInput schema / properties / sort_by

Added value: +{
+  "description": "Sort order",
+  "type": "string"
+}

addedInput schema / properties / with_genres

Added value: +{
+  "description": "Comma- or pipe-separated TMDB genre ids",
+  "type": "string"
+}

Addedv1.5.0Jul 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations the description carries full burden. It usefully discloses that a filtered page with no matches returns an empty `shows` array and that limit defaults to 10/max 20, but the default and cap merely restate schema defaults; there is no mention of auth, rate limits, or return shape beyond the empty case.

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

Conciseness4/5

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

A single dense paragraph that front-loads the core purpose (chart retrieval) before enumerating filters and limits. Every sentence carries information, though the parameter list is somewhat list-like rather than sharply prioritized.

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?

For a 14-parameter, read-only listing tool with no output schema, the description covers the essentials: default chart, filterable dimensions, pagination cap, and the empty-result behavior. It omits any description of what a returned show object contains, but the return format is largely implied and output schema is absent.

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 every parameter (including enum-constrained category and sort_by) is already documented. The description restates which filters exist but adds no format or syntax detail beyond the schema, matching the baseline 3.

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?

States a specific verb+resource ("Get a TMDB TV chart") and enumerates the chart categories (popular, top_rated, airing_today, on_the_air), which cleanly distinguishes it from sibling tmdb_movie_list and the keyword-oriented tmdb_search.

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

Usage Guidelines4/5

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

Clearly frames the tool as chart browsing with optional filter refinement, so an agent knows this is the chart/popularity entry point rather than a search. It stops short of explicitly naming an alternative (e.g. tmdb_search) or stating when-not to use it.

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

Deploy Server

tmdb_tv_list

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools