Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

justwatch_title_media

Fetch credits, video clips, and backdrop images for a JustWatch movie or show by tm/ts id. Set country and language to localize results.

Instructions

Get JustWatch title media. Returns the media for a JustWatch movie or show id (tm or ts followed by digits): credits with role, name, character and person id, video clips with provider and URL, and backdrop image URLs. country defaults to US and language to en. YouTube clips carry a watch URL. An unknown id 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 burden and does well: it enumerates the returned data (credits with roles, video clips with providers/URLs, backdrop URLs), notes defaults for country and language, and states that an unknown id returns 404. It does not explicitly confirm read-only behavior or mention rate limits, but the verb 'Get' implies a read 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?

The description is four sentences, front-loaded with the core purpose, then details of returned data, defaults, and error behavior. It is efficient with no wasted words, though the opening 'Get JustWatch title media' is slightly tautological before the elaboration.

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?

Given three simple parameters, no annotations, and no output schema, the description provides a solid picture of what is returned (credits, clips, images) and error handling (404). It could be improved by stating read-only nature explicitly or mentioning pagination if relevant, but overall it is sufficiently complete for correct invocation.

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 baseline is 3, but the description adds value by specifying default values for country (US) and language (en), which are not present in the schema. It also reiterates the id format (tm/ts followed by digits) from the schema, reinforcing parameter constraints.

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 and resource: 'Get JustWatch title media' and specifies the returned content (credits, video clips, backdrop images). It distinguishes itself from generic title tools by focusing on media, but does not explicitly name or contrast with sibling tools like justwatch_title or justwatch_title_by_id.

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?

Usage is implied: the tool requires a JustWatch id and returns media for that title. However, there is no explicit guidance on when to choose this tool over siblings such as justwatch_title or justwatch_title_by_id, nor are any exclusions stated.

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