Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

rottentomatoes_episode_reviews

Read-only

Returns the critic reviews of one Rotten Tomatoes TV episode, newest first, with stable review ids, ISO timestamps, critic identity and original article URLs. Use an episode path such as /tv/breaking_bad/s01/e01; limit reviews per page, pageable with the returned end_cursor through the available reviews (keep limit the same while paging). An episode nobody has reviewed 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_episode_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute https://www.rottentomatoes.com episode URL
pathNoRotten Tomatoes episode 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, with the same limit. 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, with the same limit. 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, with the same limit. 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, 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. 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, so safety is covered; the description still adds real behavior an agent needs: results are sorted newest first, each row carries stable ids and ISO timestamps, and an unreviewed episode yields an empty list rather than an error. It omits rate limits and any auth/browser-fallback caveats, which keeps it just under 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 sentences, front-loaded with what is returned before the invocation hint and the edge case. Slightly dense in the first sentence's field list, but every clause carries information an agent would otherwise have to infer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no elaboration, and the description still covers ordering, identity fields, pagination, and the empty-result case. What remains unaddressed is failure behavior beyond 'no reviews' (e.g., invalid path handling), which is minor for a read-only open-world scraper.

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 coverage is 100%, so every parameter is already documented in the input schema, including the type enum, the after cursor semantics, and the limit max of 20. The description mostly restates that paging contract and adds only the concrete path example; baseline 3 is appropriate when the schema does the heavy lifting.

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 critic reviews of one Rotten Tomatoes TV episode'. The episode granularity plus 'critic reviews' distinguishes it from the sibling season_reviews, movie_reviews, and critic_reviews tools without the agent needing to open 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 concrete invocation guidance ('Use an episode path such as /tv/breaking_bad/s01/e01') and paging instructions (page with end_cursor, keep limit constant). It stops short of naming alternatives or exclusions – e.g., it never says to use rottentomatoes_season_reviews for whole-season coverage or rottentomatoes_episode for episode metadata – so context is clear but not fully routed.

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