Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_monetization_titles

Fetch popular JustWatch titles by monetization type—FLATRATE, FREE, ADS, RENT, or BUY—and filter by country, language, and movie or show for streaming research.

Instructions

Get JustWatch monetization titles. Returns popular titles for one monetization type. monetization_type accepts only FLATRATE, FREE, ADS, RENT, or BUY; type accepts only all, movie, or show.

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
monetization_typeYesMonetization type: FLATRATE, FREE, ADS, RENT, BUY

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / monetization_type / enum
      Added value: +[
+  "FLATRATE",
+  "FREE",
+  "ADS",
+  "RENT",
+  "BUY"
+]
    • addedInput schema / properties / type / enum
      Added value: +[
+  "all",
+  "movie",
+  "show"
+]
  2. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the tool returns popular titles and requires a single monetization type, but says nothing about sorting, pagination, response structure, error behavior, or how optional country/language parameters affect results. This is minimal behavioral transparency for an unannotated tool.

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?

The description is two sentences with the purpose front-loaded and the constraint in the second sentence. It's efficient overall, though the second sentence redundantly repeats enum values already defined in the schema, which slightly reduces its value.

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 description covers the core behavior and required parameter constraint, but with no output schema and no annotations it should provide more context. It omits response format, ordering/sorting behavior, and how country/language options shape results. Adequate for a simple lookup tool, but with clear gaps.

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 restates the enum values for monetization_type and type that are already present in the input schema, adding no new semantic meaning. It doesn't clarify country/language code formatting or limit behavior beyond what the schema already provides.

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 states a specific verb and resource: 'Get JustWatch monetization titles' and clarifies the scope with 'Returns popular titles for one monetization type.' This distinguishes it from generic JustWatch tools, though it doesn't explicitly name any sibling alternatives.

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 usage context is implied by 'Returns popular titles for one monetization type' – an agent can infer when to use it. However, it doesn't name any sibling tools (e.g., justwatch_popular, justwatch_provider_titles) or provide explicit when-to-use/when-not-to-use guidance, leaving selection ambiguous among the many related JustWatch siblings.

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