Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_show_seasons

List a JustWatch show's seasons using its show_id, returning each season's number, title, year, description, path, and poster; set country and language as needed.

Instructions

Get JustWatch show seasons. Lists the seasons of a JustWatch show given as show_id (ts followed by digits, such as ts287292), with country defaulting to US and language to en. Each season has its number, title, year, description, path and poster. The show itself comes back with genres, scoring, runtime and offers. An unknown show returns 404.

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter country code
show_idYesRaw JustWatch show id matching ts[0-9]+
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 full burden and does a fair job: it discloses the return shape (each season has number, title, year, description, path and poster; the show itself carries genres, scoring, runtime and offers) and the error behavior ('An unknown show returns 404'). It omits pagination and auth requirements, which keeps it below 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?

Four tight sentences, front-loaded with the action and then the id format, defaults, return shape, and error case. Every sentence earns its place; nothing is padded, though the return description is slightly list-like.

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 is responsible for describing returns and it does so concretely (season fields, show-level fields, 404 case). An agent has enough to call it correctly; only pagination and permissions are unaddressed.

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. The description nonetheless adds value beyond the schema by giving a concrete id example ('ts287292') and, critically, the default values for country ('US') and language ('en'), which the schema itself does not state.

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?

Names a specific verb and resource: 'Lists the seasons of a JustWatch show.' An agent can tell this is a show-scoped season listing rather than an episode or single-season fetch. It does not explicitly name alternatives like justwatch_season_by_id or justwatch_season_episodes, so sibling differentiation is only implicit.

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 (supply a show_id of the form 'ts287292' to get its seasons) and states defaults for country and language, but it never says when to prefer this tool over the many justwatch siblings (season_by_id, season_episodes, title, title_by_id) or when not to use it. Guidance is implied, not 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