Skip to main content
Glama

rottentomatoes_movie_videos

Read-only

Returns the trailers and clips Rotten Tomatoes lists for one movie, with the video id, title, kind, duration, thumbnail, playable stream URL and video page URL. Read from Rotten Tomatoes' open video JSON endpoint using the page's primary video reference; a movie without listed videos returns an empty list. Use a movie path such as /m/clayface.

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_movie_videos"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral value beyond that: it discloses the data source (Rotten Tomatoes' open video JSON endpoint, keyed on the page's primary video reference) and the edge-case behavior that a movie with no listed videos returns an empty list.

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 sentences, front-loaded with the return payload before the sourcing detail and the usage example. No filler, and every clause carries information an agent would otherwise have to infer.

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?

An output schema exists, yet the description still briefly names the fields, and it covers the empty-list case and the data source. With both optional parameters fully documented in the schema and annotations covering safety, nothing needed to call this correctly is missing.

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 parameters are documented, so the baseline is 3. The description adds meaning on top by showing the expected path shape ('/m/clayface') and framing the lookup as deriving from the movie page, which helps an agent decide whether to supply url or path rather than guessing from the bare schema strings.

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: 'Returns the trailers and clips Rotten Tomatoes lists for one movie', and enumerates the returned fields (video id, title, kind, duration, thumbnail, stream URL, page URL). This clearly separates it from rottentomatoes_movie (general details) and rottentomatoes_movie_reviews, though it never explicitly names those alternatives.

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 final sentence 'Use a movie path such as /m/clayface' gives input-format guidance, which implies you call this after resolving a movie. But there is no explicit statement of when to pick this over rottentomatoes_movie or another video source, and no exclusions or prerequisites spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.