Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

rottentomatoes_season_reviews

Read-only

Returns the critic reviews of one Rotten Tomatoes TV season, newest first, with stable review ids, ISO created_at/updated_at timestamps, critic identity, publication and original article URLs. Use the season path such as /tv/breaking_bad/s01; limit reviews per page, pageable with the returned end_cursor through the available reviews (keep limit the same while paging). A season with no reviews yet returns an empty list.

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. Documented values: critics, top-critics, 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.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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. Changed1 schema field changed
    • 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 and audience cursors are opaque; lists can be paged up to 500 reviews deep, with the same limit that produced the cursor."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 can serve up to 500 reviews; browser fallback is capped at five pages."
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real behavioral context beyond them: result ordering, the empty-list case for seasons without reviews, and the invariant that the cursor is tied to the page size. Return-field detail (ids, timestamps, URLs) is partly redundant with the output schema, which keeps 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?

Three dense sentences with the core purpose front-loaded and pagination guidance following logically; no filler. A few clauses duplicate the input schema (limit consistency, cursor semantics), costing a point on tightness.

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 five-parameter, all-optional tool with an output schema and annotations, this covers what an agent needs: what is returned, ordering, path format, paging mechanics, and empty-state behavior. The one soft gap is that it frames output as 'critic reviews' while the `type` parameter also allows top-critics and audience, but the schema documents those values explicitly.

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; the description earns extra by giving a concrete path format example (/tv/breaking_bad/s01) that the schema's bare 'Rotten Tomatoes season path' description lacks. It also restates the limit-stability rule that the schema already documents for `after`, which is redundant but not harmful.

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 (critic reviews of one Rotten Tomatoes TV season) plus the ordering (newest first), which is enough to separate it from rottentomatoes_movie_reviews and rottentomatoes_episode_reviews by resource scope alone. It never names a sibling or explicitly excludes them, so it stops short of a 5.

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 concrete procedural guidance: supply the season path (with the /tv/breaking_bad/s01 example), page with the returned end_cursor, and keep `limit` constant across a walk. It offers no when-not guidance or routing against rottentomatoes_season or rottentomatoes_critic_reviews, so it is clear context rather than full alternative coverage.

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

All Crawlora MCP toolsInspect
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