Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_provider_titles

Retrieve popular movies and shows available on a specific streaming provider by short name, filtering by country, language, type, and result limit. Returns title details and streaming offers.

Instructions

Get JustWatch provider titles. Returns popular movies and shows available on one streaming provider, by JustWatch provider short name such as nfx, for a country (default US) and language (default en). Filter to movies or shows with type and cap results with limit (default 20, max 50). Each title has its name, year, type, poster, JustWatch URL and offers with price, currency and monetization type.

Input Schema

NameRequiredDescriptionDefault
typeNoTitle type: all, movie, show
limitNoMaximum results, defaults to 20 and clamps to 50
countryNoTwo-letter country code
languageNoTwo-letter language code
providerYesJustWatch provider short name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "all",
+  "movie",
+  "show"
+]
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden. It does disclose defaults (country US, language en, limit 20/max 50), the read-only nature of a listing query, and the returned offer fields including price, currency and monetization type. Auth and rate-limit behavior remain unstated, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then parameters, then return shape in three dense sentences with no filler. Every sentence carries information, though it is close to overpacked.

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?

With no output schema, the description compensates by enumerating returned fields (name, year, type, poster, URL, offers with price/currency/monetization). Combined with default values, an agent has enough to call and interpret results correctly; only auth/pagination details are absent.

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 goes beyond it by giving a concrete provider value example (`nfx`), restating the defaults that pair with the schema's clamping note, and clarifying that type filters to movies/shows. That example is genuinely additive for the required parameter.

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?

States a specific verb and resource ('Get JustWatch provider titles') and immediately scopes it: popular movies/shows on one streaming provider identified by short name. This is clear enough to distinguish it from justwatch_popular or justwatch_search, though it never names a sibling explicitly to route the agent.

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?

The description explains the mechanics but offers no when-to-use guidance, no exclusions, and no pointer to alternatives such as justwatch_popular, justwatch_search, or justwatch_monetization_titles. The agent must infer that this tool is for per-provider browsing.

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