Skip to main content
Glama
Grinv

TMDB MCP Server

Get compact TV show card(s)

get_tv_shows
Read-only

Quickly obtain key details (name, year, genres, vote average, episode counts) for up to 20 TV shows using TMDB IDs in a single request. Optionally add IMDb, Rotten Tomatoes, and Metacritic ratings.

Instructions

Get a compact card — name, year, genres, vote average, season/episode counts, and (opt-in) ratings — for 1-20 TV shows by TMDB id in one call. A quick way to spot short/miniseries shows (low episode count) across many candidates without a per-title get_tv call. Deliberately trimmed otherwise (no overview, the actual episode list, networks, certifications, etc.): use this for a single id too when you only need that headline info and not the full get_tv payload, not just for checking many at once. Call get_tv instead when you need the full details for a title (including region-specific certification). A bad/unknown id never fails the whole call — that entry comes back {id, found:false, reason} instead, in the same order as ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesTMDB TV show ids to fetch (1-20). Get them from search_tv/discover_tv/get_similar/get_tv_recommendations/etc.
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.
include_ratingsNoIf true, enrich every card with compact IMDb/Rotten Tomatoes/Metacritic ratings from OMDb (requires OMDB_API_KEY) — one extra OMDb lookup per id, so a large batch means a burst of OMDb calls; mind OMDb's own rate limit. Unlike get_movie/get_tv, defaults to false (off) here.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes
Behavior5/5

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

Annotations already provide readOnlyHint and openWorldHint. The description adds significant behavioral context: bad/unknown ids never fail the whole call and instead return {id, found:false, reason} in order; include_ratings defaults to false and has rate limit implications; language overrides localization. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear opening sentence, then specific details and usage guidance. It is moderately long but every sentence adds value. Slightly verbose in the middle but overall efficient.

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 presence of an output schema (not shown but mentioned), the description covers all necessary aspects: purpose, parameters, behavior on errors, use cases, and comparisons to sibling tools. It is complete for a read-only bulk lookup tool.

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 description coverage is 100% with each parameter having a description. The description adds further value: ids can be obtained from search_tv/discover_tv/etc.; language localization explanation; include_ratings defaults to false and notes OMDb rate limit. This goes beyond the schema.

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 the tool gets compact TV show cards for 1-20 shows by TMDB id. It specifies the exact data included (name, year, genres, vote average, season/episode counts, opt-in ratings) and explicitly distinguishes from get_tv by noting the trimmed payload and use case for quick scanning.

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?

The description provides explicit guidance on when to use this tool: for quick headline info, spotting short/miniseries, and checking many candidates without per-title get_tv calls. It clearly states when to use get_tv instead (when full details including region-specific certification are needed). It also explains how to obtain ids (from search_tv/discover_tv/get_similar/get_tv_recommendations).

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