Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_episode_offers

Find streaming offers for an episode by ID and country codes, returning providers, prices, and monetization details.

Instructions

Get JustWatch episode offers. Returns the streaming offers for one JustWatch episode id (tse followed by digits) across one to five comma-separated country codes in countries (default US), with language defaulting to en. Each country entry lists offers by provider, monetization type, presentation type, price and currency, with the episode details. An unknown id returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesRaw JustWatch episode id matching tse[0-9]+
languageNoTwo-letter language code
countriesNoOne to five comma-separated two-letter country codes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the return shape (offers by provider, monetization type, presentation type, price, currency, plus episode details) and that an unknown id returns 404, though it does not discuss auth or rate limits.

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?

The description is three dense sentences with the core action and scope front-loaded, and every sentence contributes relevant information. It is close to optimally concise, though the second sentence is information-heavy.

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?

There is no output schema, so the description appropriately explains the return structure and error behavior. For a three-parameter read tool, this is nearly complete, with only minor gaps around where to obtain the episode id.

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 adds useful semantics beyond the schema: default country `US`, default language `en`, the one-to-five country limit, and the `tse[0-9]+` id format.

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?

The description states a specific verb ('Get') and resource ('JustWatch episode offers'), and immediately clarifies that it returns streaming offers for one episode id. It also specifies the id format (`tse` + digits), making it clearly distinct from title- or season-level offers tools.

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?

The description gives clear operating context: one episode id, one to five comma-separated country codes defaulting to US, and a language defaulting to en. It does not explicitly name alternatives such as justwatch_episode_by_id or justwatch_title_offers, so the when-not guidance is only implicit.

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

Deploy Server

Other Tools