Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_season_by_id

Retrieve a JustWatch season's title, number, year, description, path, URL, and poster by raw ID, with optional country and language. Returns 404 if no match.

Instructions

Get JustWatch season by raw id. Looks up one JustWatch season by its raw id (tss followed by digits, such as tss297253), in the country (default US) and language (default en) you choose. Returns the season title, number, year, description, path, URL and poster. A valid id with no match returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesRaw JustWatch season id matching tss[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 full burden and does disclose real behavior: default country 'US' and language 'en', the returned fields, and the failure mode ('a valid id with no match returns 404'). It omits auth/rate-limit characteristics, but the error semantics and defaults are a meaningful disclosure for a read-only lookup.

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?

Three front-loaded sentences covering purpose, parameters, and return/failure behavior with no padding. Minor redundancy between 'Get JustWatch season by raw id' and 'Looks up one JustWatch season by its raw id' costs a point.

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, the description usefully enumerates the returned fields (title, number, year, description, path, URL, poster) and the 404 case, so it is self-sufficient for calling the tool. The missing piece is how to acquire the raw id, which belongs to usage guidance but also affects end-to-end completeness.

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 stating the default values ('US', 'en') that the schema declares only as 'Two-letter country/language code', and by giving a concrete id example (tss297253) that clarifies the tss[0-9]+ pattern.

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?

States a specific verb+resource ('Get JustWatch season') and sharpens it with the id format ('raw id', 'tss followed by digits, such as tss297253'), which distinguishes it from siblings like justwatch_episode_by_id and justwatch_season_episodes. It never explicitly names those alternatives, so it stops short of full sibling differentiation.

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 you must already hold a raw season id and does not tell the agent how to obtain one (e.g. via justwatch_search or justwatch_show_seasons), nor when to prefer this over those siblings. Usage is inferable from the id-format requirement but never stated as guidance.

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