Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_editorial_section

Fetch rendered article cards from a discovered Rotten Tomatoes editorial page, RT hub, or hub subpage; supports page-based pagination.

Instructions

Rotten Tomatoes editorial section archive. Returns the rendered article cards for a discovered editorial page, RT hub, or hub subpage. Discover paths through editorial content types pages, rt-hub, and hub-subpage. Static pages use articles_page pagination upstream; hubs use /page/{n}/.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page, default 1
pathYesDiscovered editorial section path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose real behavioral detail: pagination differs by source ('articles_page' for static pages, '/page/{n}/' for hubs) and the path must be 'discovered'. It does not cover permissions, rate limits, or what the returned cards contain beyond a phrase.

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 tight sentences, front-loaded with the purpose and followed by the return value and pagination caveat. No filler; every sentence carries information.

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?

No output schema and no annotations, so the description must stand alone. It covers what the tool returns and pagination behavior, but omits the discovery workflow details and any error/edge-case guidance for an archive-fetch tool with a required path.

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 description coverage is 100%, so both parameters are already documented in the schema. The description adds some context about the pagination mechanics tied to the page parameter and clarifies that path is 'discovered', but does not add syntax or format guidance beyond the schema.

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 resource ('editorial section archive') and what it returns ('rendered article cards for a discovered editorial page, RT hub, or hub subpage'). It names the related content types but does not explicitly contrast itself with close siblings like rottentomatoes_editorial_content, _detail, or _search.

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?

'Discover paths through editorial content types pages, rt-hub, and hub-subpage' implies a prerequisite discovery step, but the description never says when to use this tool versus the other editorial siblings (content, detail, taxonomies, search). Usage is implied rather than stated.

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