Skip to main content
Glama
Grinv

TMDB MCP Server

Get TV show details

get_tv
Read-only

Fetch complete TV show information using a TMDB ID: overview, genres, seasons, networks, creators, status, age rating, and ratings from IMDb, Rotten Tomatoes, and Metacritic, including awards.

Instructions

Get full details for one TV show by TMDB id: overview, genres, seasons/episodes counts, networks, created_by (the show's creator(s)), status, the age/content rating (certification) for region — falling back to the US rating, then any available country, when region has none; check certification_region to see which one was used — and links. By default also includes IMDb/Rotten Tomatoes/Metacritic ratings and an awards summary (see include_ratings), plus OMDb's own age rating (ratings.rated — separate from this tool's own certification above; the two can differ) from OMDb (set include_ratings=false to skip); if unavailable (no OMDB_API_KEY, no imdb_id, or the OMDb lookup fails), ratings degrades to {found:false, reason} instead of failing the call. Set expand_episodes=true to also pull every season's episode list in one extra request instead of calling get_tv_season per season. If you only need the headline info (name/year/genres/vote average, season/episode counts) — for one id or several — use get_tv_shows instead; it's trimmed on purpose and skips the rest of this payload. Get the id from search_tv.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTMDB numeric id.
regionNoISO-3166-1 country code for region-specific results (default 'US').
languageNoOverride the response language (ISO-639-1, optionally with a region), e.g. 'ru-RU' or 'en-US'. Localizes titles/overviews/genre names. Defaults to the server's TMDB_LANGUAGE.
expand_episodesNoIf true, also fetch every season's full episode list (name, air date, runtime, rating) as `seasons_detail`, in one extra request — use this instead of calling get_tv_season once per season when you need all episodes of a multi-season show. Episode overviews are omitted here to keep that aggregate response usable — call get_tv_season for one season's full detail including overview. Each season's episode list is capped at 50 (season 0 'Specials' in particular can otherwise run to hundreds of bonus clips), and the combined count across every season is capped at 250 total, and the whole aggregate additionally has a hard size ceiling (trims further if episode names are unusually long) since a 30+ season show could otherwise still exceed a usable response size even with the per-season cap alone; `episode_count` on each season still reports that season's true total. The 250 budget is spent in season order starting at season 0, so on a long-running show the specials are served first and the last seasons are the ones that fall off. A season that falls entirely beyond the 250-episode budget is skipped rather than fetched-then-discarded, so its `overview`/`poster_url` come back null too, not just its `episodes` list — call get_tv_season for that season's full detail. Defaults to false.
include_ratingsNoIf true (default), enrich the result with IMDb/Rotten Tomatoes/Metacritic ratings plus an awards summary (major-award wins/nominations — Oscars, Emmys, Golden Globes, etc., whatever OMDb aggregates; free text, not a structured count, and describes the whole film/show, not any one person's award) from OMDb (requires OMDB_API_KEY). Set false to skip the extra lookup when ratings are not needed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameNo
typeYes
genresYes
statusYes
imdb_idYes
ratingsNo
seasonsYes
taglineYes
homepageYes
imdb_urlYes
networksYes
overviewYes
tmdb_urlYes
created_byYes
media_typeYes
popularityYes
poster_urlYes
vote_countYes
vote_averageYes
certificationYes
in_productionYes
last_air_dateYes
original_nameNo
certificationsYes
first_air_dateYes
seasons_detailNo
episode_run_timeYes
number_of_seasonsYes
original_languageYes
number_of_episodesYes
last_episode_to_airYes
next_episode_to_airYes
certification_regionYes
Behavior5/5

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

Annotations (readOnlyHint, openWorldHint) are minimal, so the description carries the burden of behavioral disclosure. It goes far beyond: explains rating fallback logic (region-specific certification with fallback chain, degradation of ratings to {found:false} when OMDb unavailable), expand_episodes caps (50 per season, 250 total, trimming behavior, specials-first ordering, skipped seasons returning null), and the distinction between tool's certification and OMDb's ratings.rated. No contradictions with annotations.

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?

Though lengthy, every sentence adds essential information for a complex tool. It is front-loaded with the core purpose, then methodically covers optional behaviors and alternatives. The structure flows logically from primary details to edge cases and fallbacks, with no repetition or padding.

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

Completeness5/5

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

Given the tool's complexity (5 parameters, output schema exists, optional heavy expansions), the description is exceptionally complete. It addresses fallback scenarios, caps, degradation, alternative tools, and prerequisites. No gaps are evident for typical agent usage, and it even covers rare edge cases like trillion-épisode shows and long specials.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3, but the description substantially enriches each parameter's meaning. For expand_episodes, it details caps, trimming, ordering, and season-skip behavior. For include_ratings, it clarifies what ratings and awards summary include and the fallback behavior. For region, it explains the certification fallback chain. The extra detail is far beyond schema descriptions, making parameter semantics highly valuable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it gets full details for one TV show by TMDB ID, enumerating the specific data fields (overview, genres, seasons/episodes counts, networks, created_by, status, certification, links). It explicitly distinguishes itself from get_tv_shows ('trimmed on purpose') and get_tv_season, making its specific verb+resource+scope unmistakable.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: 'If you only need the headline info ... use get_tv_shows instead' and 'call get_tv_season for that season's full detail' for episode-level detail. Also directs users to obtain the ID via search_tv, covering prerequisites and alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/tmdb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server