Crawlora MCP

rottentomatoes_movies

Read-only

Fetch Rotten Tomatoes details for up to 20 movies in one call, in the order requested: title, synopsis, ems_id, runtime, release date and year, production companies, release runs with distributors, Tomatometer and Popcornmeter scores with their all-critics/top-critics/all-audience/verified variants, critics and audience consensus, and where_to_watch with the public streaming, rental and purchase offers (provider, link, licence, quality, price, availability date). Pass exactly one of ids (Rotten Tomatoes ems_id values) or paths (Rotten Tomatoes movie paths or URLs); identifiers that resolve to nothing are listed in not_found instead of failing the call. Review and rating counts are in the score variants (scores.critics_all.review_count is the number of critic reviews). Reviews are not included: use rottentomatoes_movie_reviews. Use rottentomatoes_movie for one title by path or URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rottentomatoes_movies"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	No	Comma-separated Rotten Tomatoes ems_id values, 1 to 20
`paths`	No	Comma-separated Rotten Tomatoes movie paths or URLs, 1 to 20

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Adds behavior annotations don't cover: partial-failure semantics ('identifiers that resolve to nothing are listed in not_found instead of failing the call'), result ordering matching input order, and the 20-item cap. It briefly clarifies where review counts live (scores.critics_all.review_count), though it stops short of describing pagination or rate/credit limits for a 20-item batch.

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-loads the core action and the batch limit before the payload list; the long field enumeration in sentence one is mostly in service of tool selection. Some of that enumeration duplicates the output schema, which costs a little tightness but not clarity.

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 2-param, 20-item batch reader with an output schema, everything an agent needs is present: batching limit, identifier types, ordering guarantee, partial-failure handling, and the sibling for reviews and single titles. Return values need not be explained further because an output schema exists.

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 earns extra by stating the mutual-exclusivity rule ('Pass exactly one of ids or paths') that the schema itself does not enforce, and by tying unresolvable identifiers to the not_found output.

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?

Opens with a specific verb, resource and batch scope ('Fetch Rotten Tomatoes details for up to 20 movies in one call'), then enumerates the payload categories returned. It also explicitly names the siblings it differs from (rottentomatoes_movie_reviews, rottentomatoes_movie), so an agent can pick it without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States when to use it (batch lookups by ems_id or path/URL) and when not to: 'Reviews are not included: use rottentomatoes_movie_reviews' and 'Use rottentomatoes_movie for one title by path or URL'. That is explicit when/when-not/alternatives routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?