Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmdb_tv_list

Retrieve TMDB TV charts—popular, top-rated, airing today, or on the air—with filters for date, rating, runtime, genres, and language. No credentials required.

Instructions

Get a TMDB TV chart. Returns a TMDB TV chart (popular, top rated, airing today, or on the air). Credential-free public TMDB data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page, default 1
limitNoMax shows, default 10, max 20
date_toNoFirst-air date upper bound (YYYY-MM-DD)
sort_byNoSort order
categoryNoTV chart, default popular
date_fromNoFirst-air date lower bound (YYYY-MM-DD)
min_votesNoMinimum vote count
max_ratingNoMaximum rating, 0-10
min_ratingNoMinimum rating, 0-10
max_runtimeNoMaximum runtime in minutes
min_runtimeNoMinimum runtime in minutes
with_genresNoComma- or pipe-separated TV genre ids: 10759,16,35,80,99,18,10751,10762,9648,10763,10764,10765,10766,10767,10768,37
include_adultNoInclude adult titles
original_languageNoTwo-letter original-language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • 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"
  2. Changed12 schema fields changed
    • 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"
+}
  3. Addedv1.5.0

TDQS

B3.3/5.0
Behavior3/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. It discloses that the data is credential-free and public, which is useful. However, it doesn't state that the operation is read-only, describe the response structure, or mention pagination/filter behavior. For a read-only list tool this is adequate but not rich.

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?

Two sentences with minimal waste, but the second sentence repeats 'Returns a TMDB TV chart' from the first. The credential-free note is useful and front-loaded after the main action. Slight redundancy prevents a 5.

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?

With 14 optional parameters, no output schema, and no annotations, the description is too sparse. It doesn't explain what a 'TV chart' returns (list of shows? metadata?), nor does it mention the filtering capabilities (date range, rating, runtime, genres) that the parameters enable. The description leaves an agent to infer the tool's full capabilities from the schema alone.

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 already documents all 14 parameters. The description adds no parameter semantics beyond the schema; it merely repeats the category enum values already present in the schema. Baseline 3 applies.

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?

States a specific verb 'Get' and resource 'TMDB TV chart', and enumerates the chart categories (popular, top rated, airing today, on the air). This clearly identifies the tool's function and distinguishes it from siblings like tmdb_tv (single show details) and tmdb_movie_list (movies), though it doesn't name them explicitly.

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

Usage Guidelines3/5

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

The description implies usage for retrieving TV charts, but provides no explicit guidance on when to choose this over tmdb_tv, tmdb_movie_list, or tmdb_search. No exclusions or alternative tool names are mentioned, leaving the agent to infer the appropriate context.

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

Deploy Server

Other Tools