Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_series

Retrieve normalized Rotten Tomatoes TV series metadata and scorecard data from a public series page without credentials by passing its path or URL.

Instructions

Rotten Tomatoes series detail. Returns normalized Rotten Tomatoes TV series metadata and scorecard data from a credential-free public series page. Pass exactly one of path or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoAbsolute https://www.rottentomatoes.com series URL
pathNoRotten Tomatoes series path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It mentions 'credential-free public series page', implying no auth needed, which is helpful. However, it does not disclose rate limits, error handling, or response structure beyond 'normalized'. This is adequate but lacks depth.

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 two sentences, front-loading the purpose and including the key usage instruction. No extraneous information; every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description only vaguely says 'metadata and scorecard data'. For a data retrieval tool, more detail on return fields or structure would improve completeness. However, sibling tools and common expectations partly compensate.

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% with descriptions for 'path' and 'url'. The description adds the constraint 'Pass exactly one of `path` or `url`', which is not in the schema, providing additional semantic value beyond the basic parameter descriptions.

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?

The description clearly states it returns 'Rotten Tomatoes TV series metadata and scorecard data', specifying the resource (series) and action (returns detail). It distinguishes from sibling tools like rottentomatoes_movie, rottentomatoes_episode, and rottentomatoes_season by focusing on series-level data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs to 'Pass exactly one of `path` or `url`', which is a clear usage guideline. However, it does not provide when-to-use vs. alternatives or when-not-to-use, though sibling names imply context.

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