Fetches a JustWatch title page and returns normalized metadata and current offers. Provide a path or URL to get structured details.
Get JustWatch title details. Fetches a JustWatch title page and returns normalized metadata and current offers. Pass exactly one of path or url.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Absolute https://www.justwatch.com title URL | |
| path | No | JustWatch title path |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description discloses it fetches a title page and returns metadata/offers, implying read-only. Lacks details on error handling, rate limits, or authentication needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler. First sentence defines purpose and output, second clarifies parameter usage. Appropriate length for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 100% schema coverage, no output schema, and low complexity, the description is adequate. Could mention it is a read operation, but the tool name implies that.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers both parameters with descriptions; description adds mutual exclusivity guidance ('exactly one'), which is not in the schema structure. Addresses 100% coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the verb (Get, Fetches) and resource (JustWatch title details, title page), and specifies outputs (normalized metadata, current offers). Distinct from sibling tools like justwatch_search or justwatch_title_by_id due to using path or URL.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Only provides parameter usage guidance ('Pass exactly one of path or url') but does not explain when to use this tool over alternatives like justwatch_title_by_id, justwatch_title_offers, etc.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.