Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_title

Pass a JustWatch path or URL to retrieve movie or show details, including title, year, genres, runtime, scores, and streaming offers.

Instructions

Get JustWatch title details. Returns the details of a JustWatch movie or show. Pass exactly one of path (such as /us/movie/inception) or url (an absolute JustWatch address). The response has the title, year, genres, runtime, content rating, scoring (IMDb and TMDB scores, tomato meter, JustWatch rating) and current offers. Titles with no offers still return metadata; a missing page returns 404.

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute https://www.justwatch.com title URL
pathNoJustWatch title path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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 burden and does well: it discloses edge-case behavior ('titles with no offers still return metadata') and the error path ('a missing page returns 404'), which are genuine behavioral traits beyond the schema. It stops short of noting rate limits or auth needs.

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?

Front-loaded with the core purpose, then the input constraint, then the return shape and edge cases. No filler sentences; every line carries information useful to calling the tool correctly.

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

Completeness4/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 compensates by enumerating the fields returned and the 404 behavior, and by stating the one-of input rule. The only missing piece is sibling routing (why this instead of justwatch_title_by_id/search), which keeps it from being fully complete.

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 100% (baseline 3), and the description adds real value on top: it gives a concrete example for path ('/us/movie/inception'), clarifies url as an absolute address, and imposes the mutually-exclusive 'pass exactly one' constraint that the empty required array does not express.

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 JustWatch title details ... details of a JustWatch movie or show'), so the agent knows exactly what it retrieves. It does not, however, differentiate from lookalike siblings such as justwatch_title_by_id or justwatch_title_offers, so an agent must infer which to pick from the parameter shape alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly guides usage by explaining that you supply a path or URL, but it never states when to prefer this tool over justwatch_search (to find a title) or justwatch_title_by_id (when you already have an ID). No explicit when/when-not or alternative routing is provided.

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