Skip to main content
Glama
TMDB MCP Server

TMDB MCP Server

Get movies in or coming to cinemas

get_movie_releases
Read-only

List movies in cinemas now or opening soon by country to check what's playing in theaters or what releases next.

Instructions

List movies in cinemas now (list='now_playing') or opening soon (list='upcoming') in one country, for 'what's playing in theaters' or 'what comes out next month'. Use get_trending for overall popularity regardless of release, discover_movies for an arbitrary date range. region filters to movies with a theatrical release in that country inside the window (a different set per country, not just a re-sort; an unrecognized code such as 'ZZ' returns an empty page, but 'XX' is a real TMDB pseudo-region). Each row's release_date is that country's release date, which can predate the window for a re-release (e.g. a 2014 film re-released this month). The window comes from TMDB and is returned as dates {minimum, maximum} (YYYY-MM-DD; same for every region; roughly the last six weeks for now_playing, the next three weeks for upcoming). TMDB's own order: roughly most popular first, not by date.

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": {
      "list": "<list>"
    },
    "name": "get_movie_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYes'now_playing' = in cinemas now; 'upcoming' = opening soon.
pageNo1-based page number for pagination (TMDB returns up to 20 results per page, max 500). Adult/softcore titles are dropped from this list, so a page can come back shorter, even empty, while total_pages/total_results stay TMDB's own; keep paging up to total_pages.
regionNoThe user's country (pass it when known), whose cinemas to list.US
languageNoResponse language (ISO-639-1, optionally with a region), e.g. 'ru-RU' or 'en-US'; pass the user's language when it isn't the default. Localizes titles/overviews/genre names. A well-formed code TMDB has no translation for (e.g. 'xx') is not an error: overviews come back null, movies/shows keep their original-language title, and episodes get a generic 'Episode N' name.en-US

Output Schema

NameRequiredDescriptionDefault
pageYes
datesYes
resultsYes
total_pagesYes
total_resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.15.0
    • addedInput schema / properties / language / default
      Added value: +"en-US"
    • changedInput schema / properties / language / description
      Previous value: -"Override 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. A well-formed code TMDB has no translation for (e.g. 'xx') is not an error: overviews come back null, movies/shows keep their original-language title, and episodes get a generic 'Episode N' name."New value: +"Response language (ISO-639-1, optionally with a region), e.g. 'ru-RU' or 'en-US'; pass the user's language when it isn't the default. Localizes titles/overviews/genre names. A well-formed code TMDB has no translation for (e.g. 'xx') is not an error: overviews come back null, movies/shows keep their original-language title, and episodes get a generic 'Episode N' name."
    • changedInput schema / properties / page / description
      Previous value: -"1-based page number for pagination (TMDB returns up to 20 results per page, max 500)."New value: +"1-based page number for pagination (TMDB returns up to 20 results per page, max 500). Adult/softcore titles are dropped from this list, so a page can come back shorter, even empty, while total_pages/total_results stay TMDB's own; keep paging up to total_pages."
    • addedInput schema / properties / region / default
      Added value: +"US"
    • changedInput schema / properties / region / description
      Previous value: -"ISO-3166-1 country code for region-specific results (default 'US')."New value: +"The user's country (pass it when known), whose cinemas to list."
  2. Addedv0.14.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds substantial behavior beyond them: an unrecognized region code returns an empty page while 'XX' is a valid TMDB pseudo-region, each row's release_date is the country-specific date and can predate the window for a re-release, the window is returned as dates {minimum, maximum} with approximate spans, and the default order is popularity rather than date. This is exactly the kind of edge-case and scoping context an agent needs.

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 front-loaded with purpose and alternative routing, then proceeds to region and date-window caveats in a logical order. It is dense and every sentence carries concrete information, but the parenthetical about 'XX' being a real TMDB pseudo-region is slightly tangential and the text could be broken into clearer blocks.

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?

For a four-parameter, read-only discovery tool with an output schema already present, the description covers the remaining ambiguity: which list to use, how region changes results, how release_date relates to the window, and what order results come in. Nothing an agent would need in order to call this correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema for region: it explains that filtering selects a different set per country inside the window, that 'ZZ' returns empty, and that 'XX' is a real pseudo-region. It also explains that release_date is country-specific and may fall outside the window, which the schema does not state. The list and page parameters are largely left to the schema, keeping it from a 5.

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 opening sentence states a specific verb and resource ('List movies in cinemas now ... or opening soon') and names the exact enum values that select each mode. It also names the two sibling tools it is not, so an agent can distinguish it from get_trending and discover_movies without opening a schema.

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 gives explicit when-to-use phrasing ('what's playing in theaters' or 'what comes out next month') and explicitly routes away: use get_trending for overall popularity and discover_movies for an arbitrary date range. It also clarifies the boundary by saying region is a theatrical-release filter, not just a re-sort.

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