Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_providers

Retrieve streaming providers tracked by JustWatch for a given country and return their IDs, names, and icon URLs. Defaults to US; invalid country codes return 400.

Instructions

Get JustWatch providers. Lists the streaming providers JustWatch tracks in a country. country is a two-letter code and defaults to US. Each provider has its id, clear name, short name, technical name and an absolute icon URL. An invalid country returns 400.

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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 reasonably well: it discloses the US default, the two-letter format constraint, and the failure behavior (an invalid country returns 400). It does not describe rate limits or whether results are cached/live, keeping it short of a 5.

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?

Four short, front-loaded sentences. The core purpose leads, the default and error behavior follow, and the return-field enumeration is compact. Every sentence carries information; nothing is padding.

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?

There is no output schema, so the description correctly compensates by enumerating returned fields (id, clear name, short name, technical name, icon URL). Combined with the default and error disclosure, an agent has everything needed to invoke 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 already 100%, so the baseline is 3. The description earns a bump by adding two pieces of semantics the schema lacks: the two-letter-code format and the fact that the parameter defaults to 'US' when omitted.

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 gives a specific verb and resource: it 'lists the streaming providers JustWatch tracks in a country.' That is concrete and unambiguous. It does not, however, distinguish itself from the many sibling listing tools (justwatch_genres, justwatch_age_certifications, justwatch_provider_titles), so it falls short of a 5.

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?

Usage is implied by the purpose — you call this to enumerate providers for a country — but there is no explicit when-to-use guidance, no mention of when NOT to use it, and no reference to an alternative sibling tool. Minimum viable but with a clear gap.

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