Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

justwatch_episode_by_id

Retrieve a JustWatch episode by raw tse id to return title, year, episode number, description, poster, paths, and streaming offers for a chosen country and language.

Instructions

Get JustWatch episode by raw id. Looks up one JustWatch episode by its raw id (tse followed by digits, such as tse5550494), in the country (default US) and language (default en) you choose. Returns the title, year, episode number, description, poster, paths, and streaming offers with provider, monetization type, presentation type, price and currency. A valid id with no match returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesRaw JustWatch episode id matching tse[0-9]+
countryNoTwo-letter country code
languageNoTwo-letter language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/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 it does meaningful work: it specifies the return payload (title, year, episode number, description, poster, paths, offers with provider/monetization/presentation/price/currency) and the 404-on-no-match behavior. Auth and rate-limit behavior are not covered, keeping it short of a 5.

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?

Front-loaded with the core action and id format, then the return payload, then the error case. No filler, though the return-field enumeration is fairly long and could be tightened.

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 provides the needed return shape and error behavior for a single-lookup tool, so an agent can call it correctly. It lacks guidance on obtaining a valid id or when to prefer a sibling lookup, which is the remaining gap.

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 beyond the schema by giving the id format example (tse5550494) and stating the country/language defaults (US/en), which the schema only labels as two-letter codes without defaults.

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 JustWatch episode by raw id') and pins down the exact resource scope (one episode). An agent can distinguish it from justwatch_season_by_id and justwatch_title_by_id purely from the name+description.

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 explains how to call it (raw id, country/language) but never says when to use it instead of siblings like justwatch_episode_offers or justwatch_season_episodes, nor how the id is obtained. Usage is implied rather than guided.

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