Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_episode

Retrieve Rotten Tomatoes TV episode details, including scorecard, parent series and season metadata, and public video data by passing an episode path or URL.

Instructions

Rotten Tomatoes episode detail. Returns Rotten Tomatoes TV episode metadata, scorecard data, parent series/season metadata, and public video metadata. Pass exactly one of path or url.

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute https://www.rottentomatoes.com episode URL
pathNoRotten Tomatoes episode path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully enumerates what is returned (episode metadata, scorecard, parent series/season metadata, public video metadata), which is real added value, but it says nothing about read-only safety, auth requirements, or rate limits.

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 short sentences, front-loaded with the identity of the resource and the return contents before the input rule. No filler, though the repeated 'Rotten Tomatoes' phrasing is slightly redundant.

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 two-input read tool with no output schema and no annotations, the description is reasonably complete: it names the resource, summarizes the returned payload, and states the mutually-exclusive input rule. Missing only exclusion guidance relative to sibling series/season/movie tools.

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 both parameters, setting the baseline at 3. The description adds genuinely new semantics beyond the schema by declaring that exactly one of `path` or `url` must be supplied — a mutual-exclusivity constraint the schema does not express (both are non-required with no oneOf).

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 and resource: returns Rotten Tomatoes TV episode metadata plus scorecard, parent series/season, and video data. An agent can tell this is an episode-detail fetcher, but it never explicitly distinguishes itself from the sibling rottentomatoes_season, rottentomatoes_series, or rottentomatoes_movie detail tools.

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?

It specifies an input constraint ('pass exactly one of path or url') but gives no guidance on when to reach for this episode tool versus the series or season tools, nor any prerequisites. Usage is only implied by the nature of a detail endpoint.

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