Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_genre_titles

Retrieve popular JustWatch titles for a specific genre, filtered by movie or show type, result limit, country, and language, to explore available streaming options by genre.

Instructions

Get JustWatch genre titles. Lists popular JustWatch titles for one genre short name in genre, such as act. type is all, movie or show (default all), limit defaults to 20 and is capped at 50, and country and language default to US and en. Each title has its id, year, path, poster, production countries and offers. Find genre names with the genres endpoint.

Input Schema

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

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

A4.5/5.0
Behavior4/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; it discloses defaults for type, limit, country and language, the 50-result cap, and the shape of each returned title (id, year, path, poster, production countries, offers). It doesn't mention pagination beyond the cap or error behavior for invalid genre names, so it falls short of exhaustive.

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?

Three compact sentences, front-loaded with the purpose, then parameter defaults, then return shape and the pointer to the genres endpoint. No filler or repetition.

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?

For a 5-parameter read tool with no output schema and no annotations, the description covers purpose, all defaults and caps, the return field set, and how to obtain a valid genre value. Nothing essential to correct invocation is missing.

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%, and the description adds value by restating defaults (type=all, limit=20 capped at 50, country=US, language=en) and giving a concrete genre example such as `act`. That example meaningfully clarifies the required parameter's expected format beyond the schema's generic 'short name' label.

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?

States a specific verb and resource ('Get JustWatch genre titles') and immediately narrows scope to 'one genre short name', which distinguishes it from search/discover siblings. The final sentence explicitly routes to the genres endpoint for genre name lookup, making sibling disambiguation concrete.

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?

Provides clear usage context: pass a genre short name like `act`, and use the genres endpoint to find valid names. It does not explicitly contrast with justwatch_discover or justwatch_popular, so alternatives are implied rather than enumerated.

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