Crawlora MCP

rottentomatoes_critic_reviews

Read-only

Returns the movie reviews written by one Rotten Tomatoes critic, newest first, with the reviewed title included as a media object carrying its path, URL and poster. Use a critic path such as /critic/mark-kermode (the /critics/mark-kermode form returned by rottentomatoes_critics_authors also works); limit reviews per page, pageable with the returned end_cursor through the available reviews (keep limit the same while paging). An unknown critic is a not-found error.

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

Name	Required	Description
`url`	No	Absolute https://www.rottentomatoes.com critic URL
`path`	No	Rotten Tomatoes critic path: /critic/{slug}. /critics/{slug} (the form critics/authors returns) and /profiles/critic/{slug} are accepted too
`after`	No	Pagination cursor: pass data.page_info.end_cursor from the previous response, with the same limit. Lists can be paged through the available reviews.
`limit`	No	Reviews 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.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

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

AddedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnly and openWorld; the description goes well beyond them by disclosing result ordering, the embedded media object's fields, the cursor invariant ('keep limit the same while paging'), and the failure mode for an unknown critic (not-found error). That is real behavioral context an agent cannot get from the annotations.

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-loads what is returned and then the path/pagination caveats; every clause carries information. The first sentence is dense with parenthetical detail, so readability suffers slightly, but there is 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?

For a paginated list tool with four optional parameters, an output schema, and read-only annotations, the description covers ordering, pagination discipline, path variants, and error behavior. Nothing an agent needs in order to call it correctly is missing.

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 already 100%, so the baseline is 3; the description adds value by clarifying that /critics/{slug} — the form returned by rottentomatoes_critics_authors — is an acceptable path, and by explaining that end_cursor is a page index times limit, which is why limit must stay fixed across a walk.

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?

States a specific verb and resource ('Returns the movie reviews written by one Rotten Tomatoes critic'), plus ordering ('newest first') and the shape of the embedded media object. That is enough to separate it from rottentomatoes_movie_reviews (reviews of a title) and rottentomatoes_critic (the critic profile) without opening any schema.

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?

Gives the concrete path form to use and points at rottentomatoes_critics_authors as the source of that path, and tells the agent to keep limit constant while walking pages via end_cursor. It does not explicitly say when to prefer this over rottentomatoes_critic or rottentomatoes_publication_reviews, so it stops just short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?