Skip to main content
Glama

Get TV season

get_tv_season
Read-only

Retrieve details and the episode list for a specific TMDB TV season by show ID and season number, with optional credits, videos, images, and provider data.

Instructions

Details for one season of a TV show, including its episode list.

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": {
      "tv_id": "<tv_id>",
      "season_number": "<season_number>"
    },
    "name": "get_tv_season"
  }
}

Input Schema

NameRequiredDescriptionDefault
tv_idYesTMDB TV show ID
appendNoExtra sections to embed in the same response: credits, aggregate_credits, videos, images, external_ids, translations, watch/providers
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.
season_numberYesSeason number, 0 for specials

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already mark this as readOnly and openWorld, so the safety profile is covered. The description still usefully adds that the response embeds the episode list; that is a real behavioral trait beyond the annotations. It says nothing about response size, pagination, or the fact that the append sections inflate the payload, though.

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?

The description is a single, front-loaded sentence with no wasted words. It is appropriately sized for a simple read tool, though it is arguably too terse given the append and language options.

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?

There is no output schema, so the description should communicate enough about the return shape; it only says 'including its episode list'. For a 4-parameter lookup with embed options, an agent still cannot tell how large the response is or what each appended section adds.

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%, and all four parameters (tv_id, season_number, append, language) are documented in the schema, including the 'season 0 for specials' convention. The description adds no meaning beyond the schema, so score 3 as the baseline.

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 gives a specific resource ('Details for one season of a TV show') and notes that the result includes an episode list. That is clear, but it never differentiates it from the sibling tools get_tv_show and get_tv_episode, so an agent must infer the boundary itself.

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?

The description offers no guidance on when to use this tool versus get_tv_show (for the show itself) or get_tv_episode (for a single episode). There are no exclusions. The only hint about when to use it is the resource name, which restates the tool's purpose.

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