TMDB MCP Server

Overview Schema Source Related Servers Discussions Admin

Get movie recommendations

get_movie_recommendations

Read-only

Fetch TMDB movie recommendations for a given movie ID using co-viewing data to surface thematically relevant titles users also liked.

Instructions

Get movies TMDB recommends for the given movie id, based on co-viewing/personalization data (what users who liked this also liked) — usually the more thematically relevant list. Prefer this over get_similar as the default choice; get_similar matches on shared genres/keywords, a blunter heuristic that can surface tonally unrelated titles. Get the id from search_movies.

Input Schema

Name	Required	Description	Default
`id`	Yes	TMDB numeric id.
`page`	No	1-based page number for pagination (TMDB returns up to 20 results per page, max 500).

Output Schema

Name	Required	Description	Default
`page`	Yes
`results`	Yes
`total_pages`	Yes
`total_results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.14.0Oct 24, 2026
- removedOutput schema / properties / results / items / properties / overview / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / overview / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / poster_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / poster_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / vote_average / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / 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 / results / items / properties / vote_average / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / vote_count / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / vote_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / year / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / year / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed2 schema fields changedv0.10.1Jul 30, 2026

changedOutput schema / properties / results / items / properties / release_date / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / results / items / properties / release_date / default
```
Added value: +null
```

Changed5 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
```

changedInput schema / properties / page / description

Previous value: -"1-based page number for pagination."New value: +"1-based page number for pagination (TMDB returns up to 20 results per page, max 500)."

changedInput schema / properties / page / maximum

Previous value: -9007199254740991New value: +500

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "page": {
+      "type": "number"
+    },
+    "results": {
+      "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"
+    },
+    "total_pages": {
+      "type": "number"
+    },
+    "total_results": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "results",
+    "page",
+    "total_pages",
+    "total_results"
+  ],
+  "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=true and openWorldHint=true, so safety and scope are covered. The description adds genuinely useful behavioral context by disclosing what the ranking is actually based on (co-viewing/personalization) and warning that get_similar can surface 'tonally unrelated titles' — a quality trait an agent can act on. It doesn't discuss result volume or pagination, though the schema already handles the latter.

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?

Front-loaded with the operation and the key routing decision, and every sentence carries usable information. Slightly longer than needed — the parenthetical gloss 'what users who liked this also liked' and the editorial 'blunter heuristic' restate the same contrast twice.

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?

An output schema exists, so return values need no explanation, and the id-provenance plus sibling routing cover the calling decision. The only soft spot is that result volume ('up to 20 per page') lives solely in the param schema rather than the description, which is acceptable here.

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 earns above that by telling the agent where the required id comes from ('Get the id from search_movies'), which the schema's 'TMDB numeric id' does not say. Pagination is left to the schema, which documents it fully.

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 and resource ('Get movies TMDB recommends for the given movie id') and immediately characterizes the underlying signal (co-viewing/personalization). It explicitly contrasts itself with the closest sibling, get_similar, so the agent can differentiate without opening either 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?

Gives an explicit default recommendation ('Prefer this over get_similar as the default choice') and explains the condition that selects the alternative ('matches on shared genres/keywords, a blunter heuristic'). It also routes to search_movies for obtaining the required id, closing the prerequisite loop.

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