Skip to main content
Glama

Get movie details

get_movie
Read-only

Fetch full details for a TMDB movie by ID—overview, runtime, genres, release date, budget, and ratings—and optionally append credits, videos, reviews, or watch providers in one call.

Instructions

Full details for a movie: overview, runtime, genres, release date, budget, ratings. Use append to embed credits, videos, recommendations, reviews, watch providers and more in one call.

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": {
      "movie_id": "<movie_id>"
    },
    "name": "get_movie"
  }
}

Input Schema

NameRequiredDescriptionDefault
appendNoExtra sections to embed in the same response: credits, videos, images, keywords, recommendations, similar, reviews, release_dates, external_ids, watch/providers, translations, alternative_titles, lists
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.
movie_idYesTMDB movie ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 profile is covered. The description usefully discloses that appended sections are embedded in the same response (one call, larger payload), but says nothing about language fallback behavior, missing/budget-zero cases, or response size implications for large appends. No contradiction 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?

Two sentences, front-loaded with the return contents and ending with the actionable optimization. The parenthetical append list partially repeats what the schema enum already enumerates, which is slightly redundant but still orients the reader before they open the schema.

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?

For a three-parameter read-only lookup with no output schema and complete schema coverage, the description supplies what is needed: what comes back and how to expand it in a single call. It omits only edge-case behavior (invalid IDs, language fallback), which is minor at this complexity.

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 coverage is 100%, so all three parameters are fully documented in the schema, which sets the baseline at 3. The description restates the append concept, but the detailed enumerations of appendable sections duplicate the schema's enum rather than adding new semantics (e.g., cost or limits of appending 20 sections).

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?

Names a specific verb and resource ("Full details for a movie") and immediately enumerates the payload fields (overview, runtime, genres, release date, budget, ratings), which cleanly separates it from siblings like get_movie_list, discover_movies, or search that return sets rather than a single movie's record.

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?

The second sentence gives real guidance on how to use this tool efficiently: batch related sections via append in one call rather than making separate requests. However, it never states when to prefer this over search or find_by_external_id to resolve a movie, nor any preconditions (e.g., having a valid TMDB ID).

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