Skip to main content
Glama

Get watch providers

get_watch_providers
Read-only

Find where a movie or TV show can be streamed, rented, or bought by country. Pass a region to get availability for one country.

Instructions

Where a movie or TV show can be streamed, rented or bought, per country (data from JustWatch). Pass region to get a single country.

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": {
      "media_type": "<media_type>",
      "id": "<id>"
    },
    "name": "get_watch_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTMDB movie or TV show ID
regionNoISO 3166-1 country, e.g. US, GB, IL
media_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description usefully adds that data is third-party (JustWatch) and that omitting region returns multiple countries, but says nothing about attribution requirements, caching, or the shape of provider categories returned.

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 short sentences, front-loaded with what the tool returns and followed by the one parameter behavior that matters. No filler or redundancy.

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?

For a three-parameter read-only lookup with no output schema, the description conveys the data domain, granularity, source, and region behavior. It stops short of describing the response structure (e.g., flatrate/rent/buy groupings), which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, with id and region documented in the schema itself. The description adds genuine meaning for region by explaining that supplying it restricts results to a single country, but media_type's enum is only obliquely covered by the phrase 'movie or TV show' and its role as a required discriminator is not spelled out.

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?

The description names a concrete resource (streaming/rental/purchase availability for a movie or TV show, broken down by country) and attributes the source to JustWatch. It is unambiguous what an agent gets back, though it does not explicitly distinguish itself from sibling retrieval tools such as get_movie.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The sentence 'Pass region to get a single country' tells the agent how to narrow scope and implies the default is multi-country, which is real usage guidance. However, there is no statement of when to reach for this tool versus alternatives, nor any prerequisite or exclusion.

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