Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_sitemap_urls

Fetch a page of Rotten Tomatoes sitemap URLs from a child sitemap; set offset and limit to page through all URLs.

Instructions

Rotten Tomatoes sitemap URL page. Returns a page of URLs from one child sitemap. Discover valid name values with rottentomatoes-sitemaps; use offset/limit to page through the complete sitemap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSitemap name returned by /rottentomatoes/sitemaps
limitNoURLs to return, default 100, max 500
offsetNoZero-based offset, default 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 burden. It discloses pagination behavior and the child-sitemap scope, but it does not mention response format, ordering, error cases, or whether repeated calls are stable. For a simple read-style paging tool this is acceptable but not fully transparent.

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 compact sentences with no filler. The core purpose is front-loaded, and the discovery/pagination instructions are packed efficiently in the second sentence. Every word earns its place.

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 simple paginated URL-list tool, the description is complete: it explains what is returned, how to find valid names, and how to page through all results. The lack of an output schema is not a problem because the return shape is inherently described as 'a page of URLs.'

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 adds meaning by clarifying that `name` comes from the sibling sitemaps tool and that `offset`/`limit` are the mechanism for walking the complete sitemap rather than just fetching one page. This goes slightly beyond the schema's basic parameter descriptions.

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?

The description states a specific verb and resource: 'Returns a page of URLs from one child sitemap.' It clearly distinguishes this tool from the sibling rottentomatoes_sitemaps by scoping it to child sitemap URL pages rather than the sitemap index itself. No tautology or ambiguity.

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?

The description explicitly tells the agent how to discover valid `name` values via rottentomatoes-sitemaps and how to page through the complete sitemap with offset/limit. It does not spell out exclusions or when not to use the tool, but the context is clear and actionable.

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