Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_season_episodes

Fetch episodes for a JustWatch season by season_id to get episode numbers, titles, descriptions, and streaming offers with provider, price, and currency. Supports country and language filters.

Instructions

Get JustWatch season episodes. Lists the episodes of a JustWatch season given as season_id (tss followed by digits), with country defaulting to US and language to en. Each episode has its number, title, description and streaming offers with provider, price and currency. Path, URL and poster appear only when JustWatch has them for that episode. An unknown season returns 404.

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter country code
languageNoTwo-letter language code
season_idYesRaw JustWatch season id matching tss[0-9]+

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses default country/language, the shape of returned episode data, conditional fields such as path/URL/poster, and 404 behavior for unknown seasons. It does not mention pagination or ordering, so it is strong but not fully exhaustive.

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 front-loaded with the core action, then moves efficiently through input format, defaults, response fields, conditional fields, and error behavior. Every sentence contributes useful information without padding.

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 three-parameter read tool with no annotations or output schema, the description covers input format, defaults, response contents, optional fields, and 404 behavior. It is nearly complete, though it could mention pagination or episode ordering if those matter to callers.

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 schema already documents the three parameters; the description still adds value by specifying that season_id looks like tss followed by digits and that country defaults to US and language to en. This goes beyond the schema's field-level 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 and resource: it gets/lists the episodes of a JustWatch season given a season_id. It is clear what the tool returns, but it does not explicitly distinguish itself from nearby JustWatch siblings such as justwatch_season_by_id or justwatch_episode_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?

The description implies usage by saying episodes are listed for a given season_id, and it notes that an unknown season returns 404. However, it gives no explicit when-to-use guidance or alternatives versus episode-level or season-detail tools, so an agent must infer the routing.

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