Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_publication_reviews

Retrieve critic reviews published by a Rotten Tomatoes outlet, newest first, using an encrypted publication ID and cursor pagination for iterative review collection.

Instructions

Rotten Tomatoes publication reviews. Returns the critic reviews one Rotten Tomatoes publication has published, newest first: stable review ids, ISO created_at/updated_at times, the critic identity, the publication name, the quote, the score sentiment and the original article URL. Pass data.page_info.end_cursor back as after for the next page, with the same limit (max 20). data.subject.kind is publication and data.subject.title is the outlet's name. An empty list is a 200 with no reviews. The id must be the encrypted publication id (encrypted_publication_id on any review row); a numeric id is rejected. data.fetched_at is the UTC fetch time.

Input Schema

NameRequiredDescriptionDefault
idYesPublication id: encrypted_publication_id
afterNoPagination cursor: pass data.page_info.end_cursor from the previous response
limitNoReviews per page, default 10, max 20. Keep it the same on every page of one walk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses ordering (newest first), pagination mechanics (end_cursor back as `after`, same `limit`), result shape for empty cases ('200 with no reviews'), id format validation, and the field list returned per row. It omits auth/permission or rate-limit traits, but covers most behavior an agent needs.

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 purpose, then pagination, then id constraints; sentences are dense and largely earn their place. The opening fragment 'Rotten Tomatoes publication reviews.' is a mild restatement of the name, and the response-shape enumeration is long, but not wasteful.

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?

No output schema exists, and the description compensates by enumerating returned fields (review ids, created_at/updated_at, critic identity, publication name, quote, sentiment, article URL) along with subject and fetched_at metadata. An agent has enough to call it correctly and interpret the response without further documentation.

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 baseline is 3, but the description adds real meaning: it reinforces that `id` is the encrypted publication id and rejects numeric ids, ties `after` to `data.page_info.end_cursor`, and explains the max-20/keep-same-limit constraint for `limit`. That is more than the schema alone conveys.

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 — critic reviews published by one Rotten Tomatoes publication, newest first — which cleanly separates it from sibling tools like rottentomatoes_critic_reviews and rottentomatoes_movie_reviews. The scope ('one publication has published') is stated up front in the first sentence.

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?

Clear context is given: you need a publication-scoped encrypted id, and the description explains where to obtain it ('encrypted_publication_id on any review row'), plus warns that a numeric id is rejected. It stops short of explicitly naming alternatives (e.g. rottentomatoes_critic_reviews, rottentomatoes_publication) or stating when not to use this tool.

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