Skip to main content
Glama
TMDB MCP Server

TMDB MCP Server

Get movie cast & crew

get_movie_credits
Read-only

Retrieve up to 20 top-billed cast members and headline crew for a movie by TMDB id, including director, writers, composer, and cinematographer. Use the id from search_movies.

Instructions

List the top-billed cast (up to 20) and the headline crew (director, writers, composer, DoP, …) of a movie by TMDB id. Get the id from search_movies.

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": {
      "id": "<id>"
    },
    "name": "get_movie_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTMDB movie id (from search_movies).

Output Schema

NameRequiredDescriptionDefault
castYes
crewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • changedInput schema / properties / id / description
      Previous value: -"TMDB numeric id."New value: +"TMDB movie id (from search_movies)."
  2. Changed2 schema fields changedv0.14.0
    • removedOutput schema / properties / cast / items / properties / character / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / cast / items / properties / character / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Addedv0.8.1
  4. Removedv0.8.1
  5. Changed3 schema fields changedv0.8.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "cast": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "character": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "id": {
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "character"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "crew": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "department": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "number"
      +          },
      +          "job": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "cast",
      +    "crew"
      +  ],
      +  "type": "object"
      +}
  6. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuine behavioral detail by disclosing truncation — cast capped at 20 and only headline crew returned, not the full crew list. It says nothing about auth, rate limits, or ordering of results, which keeps it from a 5.

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?

Two sentences with zero filler, and the scope limit plus id-source guidance are front-loaded. Every clause carries information an agent needs.

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?

With one required parameter, full schema coverage, an output schema handling return values, and annotations covering safety and open-world access, the description supplies everything still missing: the truncation limits and where to obtain the id.

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?

Only one parameter, and the schema already documents it fully (100% coverage, 'TMDB movie id (from search_movies)'). The description restates the same information rather than adding format or validity guidance beyond the schema's positive-integer constraint, so the baseline of 3 applies.

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?

States a specific verb (list) and resource (cast and crew of a movie), with explicit scope limits: top-billed cast up to 20 and headline crew only. The phrase 'of a movie by TMDB id' separates it from get_person_credits and get_tv_credits without needing their schemas.

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

Usage Guidelines4/5

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

'Get the id from search_movies' gives a concrete prerequisite and routes the agent to the right upstream tool. It stops short of stating when to prefer get_person_credits or get_tv_credits instead, so it falls one step below fully explicit alternative routing.

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