Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_movie_videos

Fetch Rotten Tomatoes movie videos and trailers by movie path or URL, returning video IDs, titles, types, durations, thumbnails, and playable stream URLs.

Instructions

Rotten Tomatoes movie videos and trailers. Returns the videos Rotten Tomatoes lists for one movie: trailers and clips with the video id, title, kind (TRAILER/OTHER), duration, thumbnail, playable stream/playlist URL and the video page URL. The primary video reference is read from the movie page and the list comes from Rotten Tomatoes' open JSON endpoint (/cnapi/videos), so it is as fast as other endpoints. A movie with no listed video returns an empty data.videos rather than an error. data.fetched_at is the UTC time the data was fetched. Pass exactly one of path or url.

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute https://www.rottentomatoes.com movie URL
pathNoRotten Tomatoes movie path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it states the data source (`/cnapi/videos`), that performance is comparable to other endpoints, that a movie with no videos yields an empty `data.videos` instead of an error, and that `data.fetched_at` is UTC fetch time. Missing only error modes other than 'no videos' (bad path/url, network failure).

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-loaded with the one-line purpose, then payload shape, then source/performance, then edge case, then the input rule. Every sentence contributes, though the endpoint/speed sentence is slightly more implementation detail than an agent needs to select the tool.

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?

There is no output schema, so the description must outline the return shape, and it does: the field list, the `TRAILER`/`OTHER` kind values, the empty-list case, and `fetched_at`. For a two-optional-param read tool this is complete enough to call correctly.

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% and both params are documented, so the schema already does the heavy lifting; the description adds the exclusivity rule ('exactly one of path or url') which is not expressed in the schema (neither is required there). That is genuine added semantics beyond the schema.

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?

First sentence names the specific resource (movie videos/trailers) and the second enumerates exactly what is returned (video id, title, kind, duration, thumbnail, stream URL, page URL). An agent can distinguish this from rottentomatoes_movie or rottentomatoes_movie_reviews without opening the schema.

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?

Clear on scope (one movie's videos) and on the input constraint 'Pass exactly one of `path` or `url`'. It does not explicitly say when to prefer this over a sibling like rottentomatoes_movie or rottentomatoes_movie_reviews, so it stops short of full alternative routing.

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