Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

justwatch_provider_titles

Retrieve popular movie and show titles by JustWatch provider short name (e.g., nfx), filtered by country, language, type, and result limit.

Instructions

Get JustWatch provider titles. Returns popular movie/show titles available through a JustWatch provider short name such as nfx.

Input Schema

TableJSON 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.5/5.0
Behavior3/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 does disclose the core behavior—returning popular movie/show titles for a provider—and implies a read-only operation, but it omits details like response shape, how limit/clamping behaves beyond the schema, and what happens with an invalid provider.

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 front-loaded sentences with no filler. The example `nfx` is useful, and the description earns its length without repeating the schema.

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 is simple and the schema covers parameter semantics well, but there is no output schema and the description does not say how to discover valid provider short names or characterize the response beyond 'popular movie/show titles.' Adequate, but with clear gaps an agent must fill by inference.

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 schema already documents all parameters. The description adds a helpful concrete example for `provider` ('such as nfx'), but it does not meaningfully explain `type`, `country`, `language`, or `limit` beyond what the schema already states.

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 clearly states a specific verb and resource: 'Get JustWatch provider titles' and goes on to say it returns popular movie/show titles by a provider short name. It does not explicitly contrast with sibling tools like justwatch_popular or justwatch_providers, so it stops short of full differentiation.

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?

The intended use case is implied: call this when you want titles available through a provider like `nfx`. However, there is no explicit guidance about when not to use it or which sibling tools to prefer instead, such as justwatch_popular or justwatch_title_offers.

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