Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_title_similar

Find similar movies and TV shows on JustWatch by raw title ID. Input an ID like tm92641 to retrieve related titles, with optional limit, country, and language.

Instructions

Get similar JustWatch titles. Returns similar titles for a raw JustWatch movie/show id such as tm92641.

Input Schema

TableJSON 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

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility. It only states the function without disclosing important behaviors such as error handling for invalid IDs, rate limits, or whether the operation is read-only. Basic transparency is lacking.

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?

The description is extremely concise with two sentences. It front-loads the purpose and provides a concrete example with zero waste. Every word earns its place.

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?

Given the tool has 4 parameters but no output schema, the description should hint at the return format. It says 'Returns similar titles' but omits details about the structure (e.g., array of IDs, objects with titles, scores). This is adequate but not fully complete.

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%, providing baseline 3. The description adds value by giving an example ID format (tm92641), which clarifies the id parameter beyond its regex pattern. However, it does not elaborate on country, language, or limit beyond what the schema already offers.

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?

The description clearly states the tool's function: 'Get similar JustWatch titles' with an example ID format. It is specific about the resource (JustWatch titles) and the action (getting similar ones). The tool is distinct from siblings like justwatch_search (which searches broadly) and justwatch_title (which retrieves details).

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 for finding similar titles when an ID is known but provides no explicit guidance on when to use this tool versus alternatives (e.g., justwatch_title_analysis). There are no exclusions or prerequisites mentioned.

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