Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

rottentomatoes_critic

Fetch a Rotten Tomatoes critic profile by path or URL, returning biography, Tomatometer approval, publication affiliations, review counts, and recent reviews.

Instructions

Rotten Tomatoes critic profile. Returns one Rotten Tomatoes critic's profile: display name, initials, vanity, encrypted critic id, biography, website, top-critic and Tomatometer-approved flags, review and publication counts, follower/following counts, critics groups, the publications they write for and their most recent reviews. The profile is read directly from Rotten Tomatoes' feed (normally a second or two), with a slower browser fallback when the feed cannot be read. An unknown critic path returns 404. Pass exactly one of path or url.

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute https://www.rottentomatoes.com critic URL
pathNoRotten Tomatoes critic path: /critic/{slug}. /critics/{slug} (the form critics/authors returns) and /profiles/critic/{slug} are accepted too

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the feed-first read (~1-2s), a slower browser fallback, and that an unknown critic path returns 404. It stops short of stating read-only-ness explicitly or any auth/rate-limit behavior, but the performance and failure semantics are valuable.

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?

Front-loaded with purpose, then return fields, then fetch semantics, then the parameter constraint. Every sentence carries information; the field enumeration is dense but relevant since there is no output schema.

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

Completeness5/5

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

No output schema exists, but the description compensates by enumerating the profile fields, plus failure (404) and fallback behavior and the one-of parameter rule. An agent has everything needed to call it correctly and know what comes back.

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, but the description adds a genuine constraint absent from the schema: the two optional params are mutually exclusive ('pass exactly one'). That is meaning beyond the schema and justifies a 4.

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 (returns a profile) and resource (a single Rotten Tomatoes critic), and enumerates the fields returned. The resource is precise enough that an agent can distinguish it from critic_reviews, critic_publications and critics_authors, though it never names those siblings explicitly.

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 'pass exactly one of path or url' rule gives parameter-level guidance but does not say when to choose this tool over alternatives like critic_reviews or critics_authors. Usage is implied by the resource, 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