Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

rottentomatoes_critic_reviews

Fetch a Rotten Tomatoes critic's published movie reviews, newest first, with publication, article URL, reviewed title and poster, plus cursor paging to walk the full list.

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: 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rottentomatoes_critic_reviews"
  }
}

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 through the available reviews.
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. Changed1 schema field changedv1.17.20
    • changedInput schema / properties / after / description
      Previous value: -"Pagination cursor: pass data.page_info.end_cursor from the previous response, with the same limit. Lists can be paged up to 500 reviews deep."New value: +"Pagination cursor: pass data.page_info.end_cursor from the previous response, with the same limit. Lists can be paged through the available reviews."
  2. Addedv1.17.18

TDQS

A4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so: it discloses ordering (newest first), data source and latency (feed_api, a second or two), a slower browser fallback capped at five pages, and precise failure semantics (200 with empty array for a critic without reviews, 404 for an unknown path). It also names the response envelope fields (data.transport, data.subject.kind/title), which an agent needs to interpret results.

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 the resource and scope, then ordered into return shape, paging, transport/fallback and error behavior. The opening pair of sentences is mildly redundant ('reviews by one critic' restated as 'movie reviews published by one critic'), but the remainder is dense with no filler.

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 must explain return values, and it does: field list, envelope metadata, pagination cursor mechanics, transport annotations and 200/404 outcomes. Nothing an agent needs in order to call and page this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents url, path, after and limit, including the cursor-is-page-index-times-limit rule. The description reinforces cursor/limit consistency during paging but adds no syntax or format meaning the schema lacks, so the baseline of 3 applies.

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') and scopes it to a single critic, which separates it from the movie- and publication-level review siblings. It stops short of naming the alternative tool for critic metadata versus critic reviews, so differentiation is implicit rather than explicit.

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?

Usage is implied by the scope phrase 'by one critic', and the paging instructions tell the agent how to walk the list. There is no explicit when-to-use/when-not-to-use guidance relative to rottentomatoes_critic, rottentomatoes_movie_reviews or rottentomatoes_publication_reviews, leaving the routing decision to inference.

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