Skip to main content
Glama
TMDB MCP Server

TMDB MCP Server

Search streaming/rental providers

search_watch_providers
Read-only

Resolve a streaming, rental, or purchase service name to its TMDB numeric provider ID for a given country, so you can filter discover results by that provider.

Instructions

Resolve a streaming/rental/purchase service's name (e.g. 'Netflix', 'Disney Plus') to its TMDB numeric provider id. Feed the id into discover_movies/discover_tv's with_watch_providers, with the same watch_region, to find top titles on that service. TMDB has no name-based lookup for this, only numeric ids, and there are hundreds of providers (296 in the US), so don't guess an id. A provider's id, and whether it's offered at all, can differ by country (checked live: Amazon Prime Video is 9 in the US, Germany and Japan but 119 in France, India and Brazil), so search in the country you'll filter in.

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": {
      "query": "<query>",
      "media_type": "<media_type>"
    },
    "name": "search_watch_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number for pagination (TMDB returns up to 20 results per page, max 500).
queryYesService name (or part of it) to look up, e.g. 'Netflix'.
media_typeYesWhether to search movie or TV providers. A service can be offered for one media type but not the other (its id stays the same either way; a movie-only or TV-only service just returns nothing from the wrong media_type).
watch_regionNoThe user's country (pass it when known), whose provider list to search; discover_* defaults its watch_region to the same country. A service not offered there comes back as no match, so retry with another country before concluding it doesn't exist.US

Output Schema

NameRequiredDescriptionDefault
pageYes
resultsYes
total_pagesYes
total_resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.15.0
    • changedInput schema / properties / media_type / description
      Previous value: -"Whether to search movie or TV providers — a service can be offered for one media type but not the other (its id stays the same either way; a movie-only or TV-only service just returns nothing from the wrong media_type)."New value: +"Whether to search movie or TV providers. A service can be offered for one media type but not the other (its id stays the same either way; a movie-only or TV-only service just returns nothing from the wrong media_type)."
    • addedInput schema / properties / watch_region / default
      Added value: +"US"
    • changedInput schema / properties / watch_region / description
      Previous value: -"Two-letter ISO-3166-1 country code, e.g. 'US'."New value: +"The user's country (pass it when known), whose provider list to search; discover_* defaults its watch_region to the same country. A service not offered there comes back as no match, so retry with another country before concluding it doesn't exist."
  2. Changed2 schema fields changedv0.14.0
    • removedOutput schema / properties / results / items / properties / logo_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / logo_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Addedv0.10.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this readOnly and open-world, but the description adds substantial context they do not cover: TMDB has no name-based lookup (ids only), there are hundreds of providers (296 in the US), and ids plus availability are country-specific, illustrated with a live-checked example of Prime Video being 9 in the US/DE/JP but 119 in FR/IN/BR. This explains why guessing fails, which is the key behavioral risk.

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 purpose and downstream chaining, then rationale for the constraints. The country-example parenthetical is long but justifies its length by proving the id-instability claim; a slightly tighter phrasing could have made the same point.

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?

Output schema exists, so return values need no explanation, and all four parameters are documented at 100% coverage. For a resolution-lookup tool chained into discover_*, nothing an agent needs in order to call it correctly or handle a no-match 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, and the description earns more by imposing a cross-tool constraint the schema cannot express: watch_region must match the region later used in discover_*. It adds little on query/media_type beyond what the schema already says, so not a 5.

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?

Starts with a precise verb+resource: resolve a service name to its TMDB numeric provider id, with concrete examples ('Netflix', 'Disney Plus'). It is sharply distinguishable from get_watch_providers (list) and from the search_* tools because the output is an id to be fed into discover_movies/discover_tv.

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 the downstream use: feed the id into discover_movies/discover_tv's with_watch_providers with the same watch_region. It also names the failure mode and remedy — do not guess an id, and retry with another country before concluding a service doesn't exist — which is exactly the when/when-not guidance an agent needs.

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