Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_genre_titles

Fetch popular JustWatch titles for a given genre short name, optionally filtered by type, country, language, and result limit.

Instructions

Get JustWatch genre titles. Returns popular titles for one JustWatch genre short name such as act. Type accepts only all, movie, or show.

Input Schema

TableJSON 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

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add useful context: results are 'popular titles' and selection is by genre short name. However, it does not disclose ordering criteria, whether country/language alter results, potential pagination behavior, or any limitations. This is acceptable for a seemingly read-only list tool but leaves room for more transparency.

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 short sentences with the main verb and resource front-loaded. The enum constraint is stated efficiently, though it somewhat duplicates the schema. Overall, every sentence earns its place and nothing is wordy.

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?

This is a moderately simple list tool, but with no output schema and no annotations, the description should clarify enough for an agent to call it confidently. It explains the main input (`genre` short name) and output domain (popular titles), but does not describe the return structure, how `country` and `language` influence results, or where to obtain genre short names. Adequate but not complete.

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 five parameters. The description adds little beyond what the schema provides: it reinforces the `type` enum and gives an example genre short name (`act`). This matches the baseline of 3 for high coverage, with only marginal added value.

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 clear verb and resource: 'Get JustWatch genre titles.' It also defines the core criterion ('for one JustWatch genre short name') with a concrete example (`act`). It does not explicitly differentiate from sibling tools like justwatch_popular or justwatch_new, but the subject and resource are specific enough that an agent can infer the tool's role.

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?

No guidance is given on when to use this tool versus alternatives such as justwatch_search, justwatch_popular, or justwatch_genres. The only directive-like sentence ('Type accepts only all, movie, or show') is a parameter constraint rather than usage guidance. The agent is left to infer appropriate use from the tool name and the genre-short-name clause.

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