Skip to main content
Glama

Get TV episode

get_tv_episode
Read-only

Fetch a single TV episode's air date, overview, guest stars, crew, rating, and optional credits or media by TMDB show, season, and episode IDs.

Instructions

Details for a single TV episode: air date, overview, guest stars, crew, rating.

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>",
      "episode_number": "<episode_number>"
    },
    "name": "get_tv_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
tv_idYesTMDB TV show ID
appendNoExtra sections to embed in the same response: credits, videos, images, external_ids, translations
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
episode_numberYesEpisode number within the season

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds that guest stars, crew, and rating are returned. It says nothing about language resolution (TMDB_LANGUAGE default) or how the append embeds change the response, which is the main behavioral nuance here.

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 front-loaded sentence fragment with zero waste; the payoff fields are listed immediately. It is a noun phrase rather than a verb phrase, but nothing is redundant.

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?

With three required parameters, an append array of five enum values, and no output schema, the description does just enough by naming the returned fields. It leaves the append semantics and language behavior undocumented, which are the places an agent is most likely to get the call wrong.

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 coverage is 100%, so all five parameters are documented in the schema itself, setting the baseline at 3. The mention of 'guest stars, crew' loosely signals that credits appear, but it does not clarify whether that requires the append parameter or whether language affects these fields.

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 resource ('a single TV episode') and enumerates the payload ('air date, overview, guest stars, crew, rating'). Its granularity distinguishes it from get_tv_season and get_tv_show by implication, though it never explicitly contrasts them.

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 prerequisites, and no mention of alternatives such as get_tv_season for bulk episode data. The agent must infer the use case from the resource name alone.

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