Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_editorial_search

Search public Rotten Tomatoes editorial articles and guides by keyword, and page through results with total-page metadata.

Instructions

Rotten Tomatoes editorial search. Searches public Rotten Tomatoes editorial content, including articles and guides. Results include content subtype plus total-page metadata.

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based result page from 1 to 10000; default 1
limitNoRows per page, default 10, range 1 to 100
queryYesEditorial search text; maximum 200 bytes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

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 full behavioral burden. It discloses that results are public and include content subtype plus total-page metadata, which is useful, but it says nothing about authentication, rate limits, ordering, or result completeness.

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 short sentences, front-loaded with the core purpose and with no filler. The opening sentence is somewhat redundant with the tool name, keeping it just short of a 5.

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?

For a three-parameter search tool with no annotations and no output schema, the description covers purpose and hints at result structure, but omits pagination behavior, relationship to the many sibling editorial tools, and any operational context such as authentication.

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 the schema already documents query, page, and limit fully. The description adds no syntax, format, or constraint details beyond that, so the baseline of 3 applies.

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 verb and resource: "Searches public Rotten Tomatoes editorial content, including articles and guides." An agent can tell it is an editorial-search tool, but the description does not distinguish it from close siblings such as rottentomatoes_editorial_content, editorial_detail, or the general rottentomatoes_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?

The coverage statement ("editorial content, including articles and guides") implies when this tool is appropriate, but there is no explicit when-to-use/when-not or any pointer to alternative Rotten Tomatoes search tools. Usage is inferable but not guided.

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