Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_genres

Fetch JustWatch genre names and short codes in your chosen language. Use the short codes to filter title searches by genre.

Instructions

Get JustWatch genres. Lists the JustWatch genres, each with its short_name (such as act) and a translated name in the language you choose (two-letter code, default en). Use the short names as the genre input of the genre titles endpoint. An invalid language returns 400.

Input Schema

NameRequiredDescriptionDefault
languageNoTwo-letter language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations the description carries the full load, and it discloses useful behavior: the returned fields (`short_name` plus translated name), the default language (`en`), and the error contract ('An invalid language returns `400`'). It stops short of describing pagination or the full response envelope, but the error and default disclosures are genuine value.

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?

Four tight sentences, front-loaded with the purpose, then output shape, then usage routing, then error behavior. Nothing redundant and no filler.

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 one-parameter lookup with no output schema, the description covers purpose, return shape, default, usage against the sibling endpoint, and the failure mode. An agent has everything needed to call it and consume the result correctly.

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%, so the baseline is 3, but the description adds meaning beyond the schema: it names the default value `en`, states the parameter controls the translated name, and gives a concrete example short name (`act`). This is more than the schema's bare 'Two-letter language code'.

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 genres') and immediately distinguishes itself from the sibling justwatch_genre_titles by explaining it supplies the `genre` input that endpoint consumes. An agent can route between the two without opening schemas.

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?

Explicitly tells the agent how to use the output: 'Use the short names as the `genre` input of the genre titles endpoint,' which is a concrete next-step context. It does not state exclusions or when not to use it, so it falls short of a 5.

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