Skip to main content
Glama

Get TV show details

get_tv_show
Read-only

Retrieve full details for a TV show, including overview, seasons, networks, status, and next or last episode; optionally append credits, videos, recommendations, and content ratings.

Instructions

Full details for a TV show: overview, seasons, networks, status, next/last episode. Use append to embed credits, videos, recommendations, content ratings and more.

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

Input Schema

NameRequiredDescriptionDefault
tv_idYesTMDB TV show ID
appendNoExtra sections to embed in the same response: credits, aggregate_credits, videos, images, keywords, recommendations, similar, reviews, content_ratings, external_ids, watch/providers, translations, alternative_titles, episode_groups
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

A3.6/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 the safety and external-fetch profile is covered. The description adds that appended sections come back embedded rather than requiring follow-up calls, which is useful, but it says nothing about error behavior for invalid IDs or rate limits on a public API.

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?

Two sentences, both front-loaded: the core payload first, then the optional expansion path. Every clause carries information and there is no filler or repetition.

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?

With no output schema, the description carries responsibility for return shape, and it does list the main returned fields plus the appendable extras. A brief note on the appendable set's limits or pagination would close the remaining gap, but the definition is sufficient to invoke the tool correctly.

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%, with tv_id, append, and language each documented including the TMDB_LANGUAGE default, so the baseline of 3 applies. The description only gestures at append's contents and says nothing about language beyond what the schema already states.

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 names a specific resource (a TV show) and enumerates the payload it returns: overview, seasons, networks, status, next/last episode. That makes it distinguishable from get_tv_season and get_tv_episode, though it never explicitly says how it differs from those siblings.

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?

It gives actionable guidance for one path: use append to embed credits, videos, recommendations and content ratings. It offers no guidance on when to prefer get_tv_season or get_tv_episode instead, so the when-not-to-use side is entirely implicit.

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