Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_search

Search JustWatch titles by query, country, and language to locate streaming options for movies and TV shows. Returns clean JSON results.

Instructions

Search JustWatch titles. Searches JustWatch titles. Country must be a two-letter ISO code such as US; language must be a two-letter code such as en.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results, defaults to 10 and clamps to 25
queryYesSearch query
countryNoTwo-letter country code
languageNoTwo-letter language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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. It never states that this is a read-only lookup, what the results contain (offers, availability, metadata), whether query matching is locale-sensitive, or any rate-limit/pagination behavior beyond the schema's limit note. Only the ISO code requirement adds context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded, but the second sentence, "Searches JustWatch titles," is a verbatim restatement of the first and earns no place. The remaining code-format sentence is useful but could be folded into one line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should describe what a match returns and how results are ordered/paged. It says nothing about result content, ranking, or default behavior when country/language are omitted, leaving an agent guessing about the response shape.

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 coverage is 100%, so all four parameters are already documented in the schema; baseline 3 applies. The description adds only marginally by restating the two-letter code requirement with examples (`US`, `en`), which the schema already conveys.

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?

States a clear verb+resource: "Search JustWatch titles." An agent knows this queries JustWatch's title catalog. However, it offers no differentiation from close siblings like justwatch_discover, justwatch_popular, justwatch_new, or justwatch_title, which also surface titles.

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 on when to pick this over justwatch_discover (browse/filter), justwatch_popular (charts), or justwatch_title (by ID). The only conditional content is code-format advice for country/language, which is parameter mechanics rather than when-to-use guidance.

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