Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

justwatch_title_by_id

Fetch details for a JustWatch movie or show using its raw ID, returning title, year, genres, runtime, rating, and available streaming offers.

Instructions

Get JustWatch title by raw id. Looks up a JustWatch movie or show by its raw id (tm or ts followed by digits, such as tm92641), with country defaulting to US and language to en. Returns the title, year, genres, runtime, content rating, description, scoring, and offers with provider, monetization type, price and currency. A valid id with no match returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesRaw JustWatch movie/show id matching tm[0-9]+ or ts[0-9]+
countryNoTwo-letter country code
languageNoTwo-letter language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 behavioral burden and does well: it lists the returned fields, states default parameter values, and specifies that a valid id with no match returns 404. It could mention read-only nature or rate limits, but the core behavior is clear.

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 sentences, front-loaded with the purpose, then the id format, defaults, return fields, and error behavior. Every sentence contributes useful information without waste.

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?

For a 3-parameter lookup tool with no output schema and no annotations, the description is quite complete: it covers purpose, input format, defaults, return contents, and error handling. Minor gaps like authentication or caching are not essential for a read-only lookup.

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%, so the baseline is 3. The description adds meaningful detail beyond the schema: it explains the raw id format with a concrete example (`tm92641`) and states the default values for country (`US`) and language (`en`), which are not in the schema descriptions.

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 specific verb ('Get/Looks up') and resource ('JustWatch title') and clarifies the required raw id format with an example. It distinguishes this lookup from generic title search by emphasizing the raw id, though it does not name a specific sibling tool as an alternative.

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 implies usage when a raw JustWatch id is available and documents default values for country and language. However, it does not explicitly say when to use this tool versus related ones like justwatch_title or justwatch_search, leaving some inference to the agent.

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