Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

rottentomatoes_critic_reviews

Fetch a Rotten Tomatoes critic's reviews newest first, with publication, article URL, and reviewed movie details; page through up to 500 reviews via cursor.

Instructions

Rotten Tomatoes reviews by one critic. Returns the movie reviews published by one critic, newest first. Each review carries a stable id, ISO created_at/updated_at, the publication, the original article URL and a media object naming the reviewed title (with its path, URL and poster). The list is pageable limit reviews at a time, up to 500 deep: pass data.page_info.end_cursor as after and keep limit the same while paging. It is read directly from Rotten Tomatoes' review feed (data.transport is feed_api, normally a second or two), with a slower browser fallback (browser_render, at most five pages) when the feed cannot be read. A critic with no reviews returns 200 with an empty reviews array; an unknown critic path returns 404. data.subject.kind is critic and data.subject.title is the reviewer's display name as Rotten Tomatoes prints it.

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
afterNoPagination cursor: pass data.page_info.end_cursor from the previous response, with the same limit. Lists can be paged up to 500 reviews deep.
limitNoReviews per page, default 10, max 20. Keep it the same on every page of one walk: the cursor is a page index times this value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations to lean on, the description carries the full load and does so: source path (data.transport=feed_api, ~1-2s), a slower browser_render fallback capped at five pages, 200-with-empty-array for a critic with no reviews, 404 for an unknown critic path, and a 500-review page ceiling. That is unusually rich error- and behavior-level disclosure.

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?

Front-loaded with purpose, then returns, then paging, then transport/error behavior – a sensible order. The single dense paragraph is long but nearly every clause carries information; only the subject.kind/subject.title detail feels like a tail-end add-on.

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?

There is no output schema, so the description compensates by enumerating the review payload (id, created_at/updated_at, publication, article URL, media object with path/URL/poster) and the subject envelope. An agent can both invoke and interpret the response without further documentation.

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 real meaning beyond the schema: the cursor must be reused with an unchanged limit because 'the cursor is a page index times this value', and total depth is capped at 500. Minor remaining gap is that url vs path precedence is not addressed in prose.

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 the movie reviews published by one critic, newest first' – which is far more precise than the name alone. Scope ('by one critic') implicitly separates it from rottentomatoes_movie_reviews and rottentomatoes_publication_reviews, but no sibling is named explicitly.

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?

Firmly establishes that this is the per-critic feed and gives concrete paging instructions ('pass data.page_info.end_cursor as `after` and keep `limit` the same while paging'). It never names an alternative tool or a when-not-to-use condition, so it stops short of a 5.

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