Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_critics_authors

Browse or search Rotten Tomatoes critic directory by name or letter, with pagination and optional inactive critics.

Instructions

Rotten Tomatoes critic directory. Returns current or inactive critics from Rotten Tomatoes' public author directory. Browse one letter or search by name; use next_cursor as after or previous_cursor as before, as indicated by the corresponding page flag. The letter values come from the live directory controls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoOpaque cursor from data.next_cursor
limitNoRows per page, default 100, range 1 to 100
beforeNoOpaque cursor from data.previous_cursor; cannot be combined with after
letterNoDirectory letter. Omit when using search; default a.
searchNoSearch critics by name; cannot be combined with letter
inactiveNoInclude the site's inactive critics list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It mentions pagination behavior, the 'inactive' flag, and that letter values come from live controls. It does not describe rate limits or response structure, but for a read-only directory query this is adequate. It adds value beyond schema by explaining cursor semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler. The purpose and primary usage patterns are front-loaded, and every phrase adds value.

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

Completeness3/5

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

While the description covers the main usage modes and pagination, it does not mention what the response contains (e.g., critic names, IDs, bios). With no output schema, an agent might not know how to interpret results. For a list tool with six parameters, slightly more detail on the expected payload would improve completeness.

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 parameters are already described. The description adds useful context: explains that 'after' and 'before' correspond to 'next_cursor' and 'previous_cursor', and that letter values are sourced from live controls. This enhances understanding beyond the schema's terse definitions.

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?

Clearly states it returns critics from Rotten Tomatoes' public author directory, with explicit actions (browse by letter or search by name). This differentiates it from sibling tools like rottentomatoes_movie or rottentomatoes_person, which target different entities.

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?

Provides explicit instructions on pagination (using 'after'/'before' with cursor values) and the two modes (letter browsing vs. name search). It does not explicitly contrast with alternative tools, but the scope is clear enough from the name and purpose.

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