TMDB MCP Server

Overview Schema Source Related Servers Discussions Admin

Get movie cast & crew

get_movie_credits

Read-only

Retrieve a movie's top-billed cast and headline crew—director, writers, composer, and director of photography—by TMDB id to see who starred in or created it.

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.

Input Schema

Name	Required	Description	Default
`id`	Yes	TMDB numeric id.

Output Schema

Name	Required	Description	Default
`cast`	Yes
`crew`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.14.0Oct 24, 2026
- 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"
+]
```
Addedv0.8.1Jul 26, 2026
Removedv0.8.1Jul 26, 2026

Changed3 schema fields changedv0.8.0Jul 22, 2026

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"
+}

First observedv0.3.0Jul 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context the annotations do not: results are truncated to the top 20 cast and a curated 'headline' crew list (director, writers, composer, DoP), so the agent knows this is not the full credit roll.

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, no filler, with the scope and the 20-item cap front-loaded before the id-sourcing instruction. Every clause carries information.

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?

Low-complexity single-parameter read tool with an output schema and read-only annotations; the description covers scope, truncation limits, and id provenance. Nothing further is needed to select and invoke it correctly.

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 coverage is 100% and the single parameter is already described as 'TMDB numeric id.' The description adds the practical step of sourcing that id from search_movies, which is value 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?

Specific verb ("List") plus precise resource scope: top-billed cast (capped at 20) and headline crew roles for a movie. It is clearly distinguishable from sibling get_tv_credits (TV) and get_person_credits (by person) 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 Guidelines4/5

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

Explicitly routes the agent to search_movies to obtain the required TMDB id, which is the main prerequisite. It does not state exclusions (e.g. use get_tv_credits for TV shows), so it stops short of full when/when-not guidance.

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