Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

rottentomatoes_season_reviews

Retrieve Rotten Tomatoes TV season reviews for critics, top critics, or audience, including critic identity and article URLs, with cursor pagination for sequential review collection.

Instructions

Rotten Tomatoes TV season critic reviews. Returns the critic reviews of one TV season, newest first. Each review has a stable id, ISO created_at/updated_at timestamps, the critic identity and the original article URL. 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 about a second); if the feed cannot be read, the service may fall back to loading the season's reviews page in a browser (transport: browser_render, much slower and at most five pages deep). A season with no critic reviews yet returns 200 with an empty reviews array. data.subject identifies the season. data.fetched_at, X-Cache and X-Availability-Last-Success-* describe freshness. Pass exactly one of path or url.

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_season_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute https://www.rottentomatoes.com season URL
pathNoRotten Tomatoes season path
typeNoReview list: critics (default), top-critics or audience.
afterNoPagination cursor: pass data.page_info.end_cursor from the previous response. Critic cursors are base64 page indexes; audience cursors are opaque keyset values that should be passed back unchanged. The feed has no 500-review ceiling; browser fallback is capped at five pages.
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. Critic cursors are base64 page indexes; audience cursors are opaque keyset values that should be passed back unchanged. The feed can serve up to 500 reviews; browser fallback is capped at five pages."New value: +"Pagination cursor: pass data.page_info.end_cursor from the previous response. Critic cursors are base64 page indexes; audience cursors are opaque keyset values that should be passed back unchanged. The feed has no 500-review ceiling; browser fallback is capped at five pages."
  2. Addedv1.17.18

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the newest-first ordering, the feed_api path (~1s) with a browser_render fallback capped at five pages, a 200/empty-array response for seasons with no reviews, and freshness fields. It doesn't state rate limits or auth requirements, keeping it from a 5.

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?

The opening sentence front-loads the resource and ordering, and the paging mechanics are grouped logically. It is dense but nearly every clause carries operational information; the `data.fetched_at`/`X-Cache` freshness sentence is the closest thing to 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?

Five optional parameters, an enum, and no output schema – the description covers the identifier choice, pagination contract, fallback behavior, and empty-result case, which is everything needed to call it correctly and interpret the response envelope.

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, and the description genuinely adds beyond it by explaining the cursor contract: pass `data.page_info.end_cursor` as `after` and keep `limit` constant because the cursor is a page index multiplied by the limit. It also notes that there is no 500-review ceiling on the feed while browser fallback is capped at five pages.

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?

The description states a specific verb and resource ("Returns the critic reviews of one TV season, newest first") and names the season subject explicitly. It also distinguishes the `type` variants (critics, top-critics, audience) and sits clearly apart from movie/episode review siblings.

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 tells the agent to pass exactly one of `path` or `url` and explains the paging loop concretely, which is real usage guidance. But it never says when to pick this over `rottentomatoes_critic_reviews` or `rottentomatoes_episode_reviews`, and no prerequisite for the season identifier is given.

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