Skip to main content
Glama

Get TV chart

get_tv_list
Read-only

Retrieve a curated TV chart for popular, top-rated, airing-today, or upcoming-7-day shows, with optional page and language filters.

Instructions

A curated TV chart: popular, top_rated, airing_today or on_the_air (airing in the next 7 days).

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": {
      "list": "<list>"
    },
    "name": "get_tv_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYes
pageNoResults page, 1-500. Each page holds up to 20 results.
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds only the clarification that on_the_air means airing within the next seven days; it says nothing about authentication, rate limits, pagination behavior, or the return shape.

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 front-loaded sentence with no filler, appropriately sized for a simple retrieval tool. The fragment style is efficient and every phrase contributes to identifying the chart categories.

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

Completeness3/5

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

For a simple read-only list tool, the core selection input is explained, but with no output schema the description never states that results are TV shows or what the returned records contain. It also omits sibling routing, leaving meaningful contextual gaps.

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

Parameters4/5

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

Schema description coverage is 67%, and the description adds meaning to the required list parameter by naming the chart categories and defining on_the_air. Page and language are already documented in the schema, so the added semantics are useful but not exhaustive.

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 identifies the resource as a curated TV chart and enumerates the four chart types, so an agent can tell what it returns. It lacks an explicit verb such as 'retrieve' and does not distinguish this tool from siblings like discover_tv or get_trending, so it is clear but not fully differentiating.

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?

There is no when-to-use guidance, no exclusions, and no routing against alternatives. The category enumeration describes the list parameter rather than explaining when this tool should be chosen over search, discover_tv, or get_trending.

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