TMDB MCP Server

Overview Schema Source Related Servers Discussions Admin

Get a movie collection

get_collection

Read-only

Retrieve a movie franchise and all its parts in release order by TMDB collection ID, so you can view the complete series chronology.

Instructions

Get a movie collection/franchise and all its parts in release order (e.g. the whole 'The Dark Knight Collection'). Get the collection id from search_collections (by franchise name) or from a movie's collection field in get_movie.

Input Schema

Name	Required	Description	Default
`id`	Yes	TMDB numeric id.
`language`	No	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.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`parts`	Yes
`overview`	Yes
`poster_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv0.14.0Oct 24, 2026

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."New 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."

removedOutput schema / properties / overview / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / overview / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / parts / items / properties / overview / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / parts / items / properties / overview / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / parts / items / properties / poster_url / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / parts / items / properties / poster_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / parts / items / properties / vote_average / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / parts / items / properties / vote_average / description

Added value: +"TMDB's own 0-10 user score. A different audience and scale from the IMDb/RT/Metacritic scores get_movie/get_tv return as `ratings` — don't compare, average or substitute across the two."

addedOutput schema / properties / parts / items / properties / vote_average / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / parts / items / properties / vote_count / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / parts / items / properties / vote_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / parts / items / properties / year / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / parts / items / properties / year / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / poster_url / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / poster_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Addedv0.10.1Jul 30, 2026
Removedv0.8.1Jul 26, 2026
Changed2 schema fields changedv0.8.1Jul 26, 2026
- removedInput schema / properties / language / minLength
```
Removed value: -2
```
- addedInput schema / properties / language / pattern
```
Added value: +"^[a-z]{2}(-[A-Z]{2})?$"
```

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": {
+    "id": {
+      "type": "number"
+    },
+    "name": {
+      "type": "string"
+    },
+    "overview": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "parts": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "number"
+          },
+          "media_type": {
+            "const": "movie",
+            "type": "string"
+          },
+          "original_title": {
+            "type": "string"
+          },
+          "overview": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "poster_url": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "release_date": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "vote_average": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "vote_count": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "year": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "media_type",
+          "year",
+          "release_date",
+          "vote_average",
+          "vote_count",
+          "overview",
+          "poster_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "poster_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "overview",
+    "poster_url",
+    "parts"
+  ],
+  "type": "object"
+}

First observedv0.3.0Jul 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds a real behavioral detail not in annotations: results include every part of the franchise and are returned in release order. It doesn't discuss failure modes (bad id) or localization interaction with the language parameter, keeping it short of 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, front-loaded with what the tool returns and followed by the prerequisite for calling it. No filler, no repetition of schema content.

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 an output schema present and annotations covering safety, the description only needs to add scope, ordering, and id provenance — and it does all three. Nothing an agent needs to call it 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 coverage is 100%, so the baseline is 3; the description nevertheless adds meaning to `id` beyond 'TMDB numeric id' by explaining its two authoritative sources. The `language` parameter is left entirely to the schema, which documents it thoroughly.

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 (get) plus resource (movie collection/franchise) plus a scope guarantee (all parts in release order), with a concrete example ('The Dark Knight Collection'). An agent can distinguish it from search_collections or get_movie without opening the 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?

Explicitly states how to obtain the required id — from search_collections by franchise name, or from a movie's `collection` field in get_movie — which routes the agent to the correct preceding tool. It also implicitly excludes use of this tool for lookup-by-name.

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