Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

justwatch_title_offers

Fetch streaming offers and pricing for a JustWatch movie or show ID across up to five country codes, including provider, monetization type, and currency.

Instructions

Get JustWatch title offers. Returns the streaming offers for a JustWatch movie or show id across one to five comma-separated country codes in countries (default US), with language defaulting to en. Each country entry has its offers (provider, monetization type, presentation type, price, currency) and the title details. An unknown id returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesRaw JustWatch movie/show id matching tm[0-9]+ or ts[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

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the per-country payload (provider, monetization type, presentation type, price, currency, plus title details) and discloses error behavior ('An unknown id returns 404'). It stops short of stating read-only/safety character or any rate limits, but the behavioral picture is largely complete.

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?

Three short sentences, front-loaded with purpose and then parameters, with no padding. The opening 'Get JustWatch title offers' is mildly redundant against the following sentence, keeping it just under a 5.

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?

No output schema exists, and the description compensates by describing the returned structure and the 404 failure mode, which is the key missing information for this 3-param read tool. The remaining gap is that it never explains where a valid `id` comes from.

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 already 100%, so the baseline is 3; the description earns above-baseline credit by supplying the defaults that the schema omits (countries defaults to 'US', language defaults to 'en') and restating the one-to-five comma-separated format of countries.

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 pairs a specific verb and resource ('Get JustWatch title offers. Returns the streaming offers for a JustWatch movie or show id'), making the function unambiguous on its own. It does not, however, distinguish itself from close siblings such as justwatch_title, justwatch_title_by_id, or justwatch_title_media, so an agent still has to infer which of the justwatch_title_* family to pick.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no mention of how to obtain the required `id` (e.g. via justwatch_search), and no exclusion relative to the many sibling tools. Usage is only weakly implied by 'for a JustWatch movie or show id'.

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