Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

justwatch_new

Fetch newly added movies and shows from JustWatch by type, country, and language, with a limit of up to 50 results.

Instructions

Get new JustWatch titles. Returns newly available movies and shows. Type accepts only all, movie, or show; limit defaults to 20 and clamps to 50.

Input Schema

NameRequiredDescriptionDefault
typeNoTitle type: all, movie, show
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

C2.9/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 behavioral burden. It notes the return content but never defines what "new" means (time window, region dependence), says nothing about pagination, ordering, whether country/language affect results, or that it is a safe read-only operation.

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?

Three short sentences that front-load the purpose before the parameter constraints. Slightly redundant since the parameter sentence duplicates schema content, but there is little wasted text.

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?

For a four-parameter, optional-only listing tool with no output schema, the description is minimally adequate: it covers purpose and parameter constraints. It omits the definition of "new," default behavior for country/language, and any routing among the many justwatch siblings, which are real gaps for correct invocation.

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 enum values and the limit default/clamp are already documented in the schema. The description repeats "Type accepts only all, movie, or show; limit defaults to 20 and clamps to 50" without adding meaning beyond the schema, so the baseline 3 applies.

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 specific verb and resource ("Get new JustWatch titles") and clarifies the return content ("newly available movies and shows"). However, it does not distinguish this from closely related siblings such as justwatch_popular, justwatch_discover, or justwatch_genre_titles, so the agent must infer the difference from the name alone.

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?

There is no explicit when-to-use guidance, no mention of when NOT to use it, and no naming of alternatives like justwatch_popular or justwatch_search. The only implied usage is "newly available" titles, which the agent must interpret on its own.

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