TMDB MCP Server

Overview Schema Source Related Servers Discussions Admin

Where to watch

get_watch_providers

Read-only

Find where a movie or TV show can be streamed, rented, or bought in a specific country, returning provider names by access type and alternate regions when data is unavailable.

Instructions

Find where a movie or TV show can be streamed, rented or bought in a given country (JustWatch data via TMDB). Returns provider names per access type for that country; if it has no data, returns available:false plus available_regions to retry with. Get the id from search_movies/search_tv.

Input Schema

Name	Required	Description
`id`	Yes	TMDB numeric id.
`region`	No	ISO-3166-1 country code for region-specific results (default 'US').
`media_type`	Yes	Media type: 'movie' or 'tv'.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.14.0Oct 24, 2026

changedOutput schema / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "available": {
-        "const": false,
-        "type": "boolean"
-      },
-      "available_regions": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "region": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "region",
-      "available",
-      "available_regions"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "ads": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "available": {
-        "const": true,
-        "type": "boolean"
-      },
-      "available_regions": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "buy": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "free": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "link": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "region": {
-        "type": "string"
-      },
-      "rent": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "streaming": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "region",
-      "available",
-      "link",
-      "streaming",
-      "free",
-      "ads",
-      "rent",
-      "buy",
-      "available_regions"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "available": {
+        "const": false,
+        "type": "boolean"
+      },
+      "available_regions": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "region": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "region",
+      "available",
+      "available_regions"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "ads": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "available": {
+        "const": true,
+        "type": "boolean"
+      },
+      "available_regions": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "buy": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "free": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "link": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "region": {
+        "type": "string"
+      },
+      "rent": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "streaming": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "region",
+      "available",
+      "link",
+      "streaming",
+      "free",
+      "ads",
+      "rent",
+      "buy",
+      "available_regions"
+    ],
+    "type": "object"
+  }
+]

Changed1 schema field changedv0.10.1Jul 30, 2026

changedInput schema / properties / media_type / description

Previous value: -"Whether the id refers to a movie or a TV show."New value: +"Media type: 'movie' or 'tv'."

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",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "available": {
+          "const": false,
+          "type": "boolean"
+        },
+        "available_regions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "region": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "region",
+        "available",
+        "available_regions"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "ads": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "available": {
+          "const": true,
+          "type": "boolean"
+        },
+        "available_regions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "buy": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "free": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "link": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "region": {
+          "type": "string"
+        },
+        "rent": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "streaming": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "region",
+        "available",
+        "link",
+        "streaming",
+        "free",
+        "ads",
+        "rent",
+        "buy",
+        "available_regions"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedv0.3.0Jul 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only cover readOnly and openWorld, so the description carries the rest: it discloses the return shape (provider names per access type per country) and the failure mode (`available:false` plus `available_regions`), which is genuinely actionable behavior an agent could not infer from annotations alone. It does not mention rate limits, caching, or data freshness, which is the only remaining gap.

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?

Three tight sentences, front-loaded with the core purpose, then return/fallback behavior, then the id prerequisite. No filler or restated name/title.

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?

An output schema exists so return values need not be fully spelled out, yet the description still flags the one non-obvious return case (available:false with available_regions). Combined with full param coverage and the id-sourcing hint, an agent has everything needed to call 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%, so baseline is 3. The description still adds value by tying `region` to country-scoped results and by establishing where `id` must come from (search_movies/search_tv), which is workflow semantics not present in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Find where a movie or TV show can be streamed, rented or bought in a given country', plus the data provenance (JustWatch via TMDB). It is clearly distinguishable from data-retrieval siblings like get_movie or search_watch_providers, though it never names the closest sibling (search_watch_providers) explicitly.

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?

Gives the concrete prerequisite and upstream alternative: 'Get the id from search_movies/search_tv', which tells the agent the required call order. It also explains what to do when the result is empty (retry with available_regions). No explicit when-not-to-use or sibling exclusion is stated.

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