Skip to main content
Glama
Grinv

TMDB MCP Server

Get movie details

get_movie
Read-only

Retrieve full movie details by TMDB ID: overview, genres, runtime, budget, revenue, age rating, and links to TMDB and IMDb. Optionally includes ratings from Rotten Tomatoes, Metacritic, and awards summary.

Instructions

Get full details for one movie by TMDB id: overview, genres, runtime, budget/revenue, vote average, 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 (TMDB + IMDb). By default also includes IMDb/Rotten Tomatoes/Metacritic ratings, an awards summary (major-award wins/nominations — Oscars, Emmys, Golden Globes, etc.; free text, not a structured count, for the whole film/show, not one person), and 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. If you only need the headline info (title/year/genres/vote average) — for one id or several — use get_movies instead; it's trimmed on purpose and skips the rest of this payload. Get the id from search_movies.

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.
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
yearYes
titleNo
genresYes
statusYes
imdb_idYes
ratingsNo
taglineYes
homepageYes
imdb_urlYes
overviewYes
tmdb_urlYes
budget_usdYes
collectionYes
media_typeYes
popularityYes
poster_urlYes
vote_countYes
revenue_usdYes
release_dateYes
vote_averageYes
certificationYes
certificationsYes
origin_countryYes
original_titleNo
runtime_minutesYes
spoken_languagesYes
original_languageYes
certification_regionYes
production_companiesYes
Behavior5/5

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

The description discloses OMDb enrichment behavior, region certification fallback, and ratings degradation (returning found:false on failure). These details go beyond the readOnlyHint and openWorldHint annotations, providing clear behavioral context.

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 lengthy but each sentence serves a purpose, front-loading the main purpose. Minor redundancy (e.g., repeated explanation of awards summary) could be trimmed, but overall it is well-structured.

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 (4 parameters, nested output schema), the description covers all critical aspects: main payload, fallback behaviors, optional OMDb data, and relationship to sibling tools. No gaps are evident.

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%, but the description adds significant meaning: explains region fallback, clarifies language localization, and details include_ratings enrichment and fallback. This surpasses baseline 3 by providing richer context than the schema alone.

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 that the tool returns full movie details for one TMDB ID, listing specific fields (overview, genres, runtime, etc.). It explicitly distinguishes itself from the sibling tool 'get_movies' which provides only headline info for one or multiple IDs.

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 vs 'get_movies', advises getting the ID from 'search_movies', and explains optional parameter behavior (e.g., setting include_ratings=false to skip OMDb lookup). It also details region fallback logic.

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