Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_title_similar

Find similar JustWatch movies and shows by tm/ts ID. Returns IDs, types, titles, years, posters, and offers filtered by country and language.

Instructions

Get similar JustWatch titles. Lists titles similar to a JustWatch movie or show id (tm or ts followed by digits). limit defaults to 10 and is capped at 25; country defaults to US and language to en. Each result has its id, type, title, year, path, poster, production countries and offers. An unknown id returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesRaw JustWatch movie/show id matching tm[0-9]+ or ts[0-9]+
limitNoMaximum results, defaults to 10 and clamps to 25
countryNoTwo-letter country code
languageNoTwo-letter language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/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 and does so well: it discloses defaults and caps (limit 10/25, country US, language en), enumerates the returned fields, and specifies that an unknown id yields a 404. It stops short of stating read-only semantics explicitly, but the disclosure is substantial.

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 purpose, then id format, then defaults, then return shape and error case. Four sentences, each carrying distinct information with 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?

With no output schema, the description appropriately enumerates the returned fields and covers input format, defaults, and the 404 error path. An agent has everything needed to call it and interpret the response 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 100%, so the baseline is 3, but the description adds value beyond the schema by giving the country (US) and language (en) defaults, which the schema does not mention, and restates the id format constraint. The added defaults justify a notch above baseline.

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 similar JustWatch titles') and constrains the input to a JustWatch movie/show id in tm/ts form. An agent can distinguish it from siblings like justwatch_title or justwatch_title_analysis without opening a schema.

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 the precondition that you must already hold a JustWatch id (tm/ts...), but it never states when to use this versus alternatives such as justwatch_search (to find an id) or the other justwatch_title_* siblings. Usage is inferable but not explicit, and no exclusions are given.

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