Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_popular

Fetch popular JustWatch movies and shows by type, country, and language, with cursor pagination and a configurable result limit.

Instructions

Get popular JustWatch titles. Returns popular movies and shows from the public JustWatch website GraphQL endpoint. Type accepts only all, movie, or show; limit defaults to 20 and clamps to 50.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoTitle type: all, movie, show
limitNoMaximum results, defaults to 20 and clamps to 50
cursorNoOpaque next_cursor from the prior response; omit for the first page
countryNoTwo-letter country code
languageNoTwo-letter language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque next_cursor from the prior response; omit for the first page",
+  "type": "string"
+}
    • addedInput schema / properties / type / enum
      Added value: +[
+  "all",
+  "movie",
+  "show"
+]
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It states the data source (public JustWatch GraphQL endpoint), restricts the type values, and documents the default and cap on limit. It does not detail response shape or pagination, but for a public read-only listing tool this is reasonable.

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 tight sentences: the first states the core action and output, the second packs the important constraints. No filler or redundant explanatory material.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has five optional parameters and no output schema, so an agent must rely on the description for behavior. It covers the main purpose and constraints, but doesn't describe the response format or how cursor-based pagination works, beyond what the schema already says.

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 description coverage is 100%, so the baseline is 3. The description's type and limit notes essentially repeat the schema descriptions and add no deeper semantics for cursor, country, or language.

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 uses a specific verb and resource ('Get popular JustWatch titles') and clarifies the output scope ('popular movies and shows'). This clearly distinguishes it from sibling JustWatch tools like justwatch_search, justwatch_title_by_id, and justwatch_new without requiring schema inspection.

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 phrase 'popular JustWatch titles' gives an agent a clear context for when to select this tool. It does not explicitly enumerate exclusions or recommend alternatives such as justwatch_search for keyword queries, but the primary use case is unambiguous.

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