Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_browse_movies

Browse Rotten Tomatoes movie listings for in theaters, at home, or coming soon; filter by genre, critic and audience scores, rating, or streaming service with cursor pagination.

Instructions

Rotten Tomatoes movie discovery rows. Returns movie rows from Rotten Tomatoes' browse listing. Use /rottentomatoes/browse/filters to discover current values for each list. Filters accept comma-separated values; pagination uses the opaque after cursor from the previous response.

Input Schema

NameRequiredDescriptionDefault
listNoMovie browse list: movies_in_theaters, movies_at_home, movies_coming_soon
sortNoSort value from the selected list's browse/filters response
afterNoOpaque next-page cursor returned in data.page_info.end_cursor
limitNoRows to return, default 30 (one full page), max 30. The cursor always moves past the whole 30-row page, so keep the default when paging
genresNoComma-separated genre values from browse/filters
criticsNoComma-separated Tomatometer values from browse/filters
ratingsNoComma-separated content ratings from browse/filters
audienceNoComma-separated Popcornmeter values from browse/filters
affiliatesNoComma-separated streaming/service values from browse/filters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.18
    • changedInput schema / properties / limit / description
      Previous value: -"Rows to return, default 10, max 30"New value: +"Rows to return, default 30 (one full page), max 30. The cursor always moves past the whole 30-row page, so keep the default when paging"
  2. Changed10 schema fields changedv1.17.5
    • addedInput schema / properties / affiliates
      Added value: +{
+  "description": "Comma-separated streaming/service values from browse/filters",
+  "enum": [
+    "theaters",
+    "fandango",
+    "apple-tv-plus",
+    "netflix",
+    "prime-video",
+    "disney-plus",
+    "max",
+    "peacock",
+    "hulu",
+    "paramount-plus",
+    "amc-plus",
+    "acorn-tv",
+    "apple-tv"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / after
      Added value: +{
+  "description": "Opaque next-page cursor returned in data.page_info.end_cursor",
+  "type": "string"
+}
    • addedInput schema / properties / audience
      Added value: +{
+  "description": "Comma-separated Popcornmeter values from browse/filters",
+  "enum": [
+    "verified_hot",
+    "upright",
+    "spilled"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / critics
      Added value: +{
+  "description": "Comma-separated Tomatometer values from browse/filters",
+  "enum": [
+    "certified_fresh",
+    "fresh",
+    "rotten"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / genres
      Added value: +{
+  "description": "Comma-separated genre values from browse/filters",
+  "enum": [
+    "action",
+    "adventure",
+    "animation",
+    "anime",
+    "biography",
+    "comedy",
+    "crime",
+    "documentary",
+    "drama",
+    "entertainment",
+    "faith_and_spirituality",
+    "fantasy",
+    "game_show",
+    "lgbtq",
+    "health_and_wellness",
+    "history",
+    "holiday",
+    "horror",
+    "house_and_garden",
+    "kids_and_family",
+    "music",
+    "musical",
+    "mystery_and_thriller",
+    "nature",
+    "news",
+    "reality",
+    "romance",
+    "sci_fi",
+    "short",
+    "soap",
+    "special_interest",
+    "sports",
+    "stand_up",
+    "talk_show",
+    "travel",
+    "variety",
+    "war",
+    "western"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Rows to return, default 10, max 20"New value: +"Rows to return, default 10, max 30"
    • addedInput schema / properties / list / enum
      Added value: +[
+  "movies_in_theaters",
+  "movies_at_home",
+  "movies_coming_soon"
+]
    • addedInput schema / properties / ratings
      Added value: +{
+  "description": "Comma-separated content ratings from browse/filters",
+  "enum": [
+    "g",
+    "pg",
+    "pg_13",
+    "r",
+    "nc_17",
+    "nr",
+    "ur"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / sort / description
      Previous value: -"Sort: popular, newest, top_box_office"New value: +"Sort value from the selected list's browse/filters response"
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "popular",
+  "newest",
+  "top_box_office",
+  "a_z",
+  "critic_highest",
+  "critic_lowest",
+  "audience_highest",
+  "audience_lowest"
+]
  3. Addedv1.1.0

TDQS

A3.6/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 two useful traits beyond the schema: filters accept comma-separated values and pagination is cursor-based on an opaque `after` token. It says nothing about read-only nature (implied), return shape of a row, or what happens when a filter value is stale, leaving gaps for a 9-param tool.

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?

Four short sentences, front-loaded with what is returned, followed by the dependency and pagination rules. The opening 'Rotten Tomatoes movie discovery rows' is slightly redundant with the sentence that follows, but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers filtering, value discovery, and pagination for a tool whose parameters are fully schema-documented and which has no output schema. It omits any sense of what a movie row contains and the page-size constraint, though the latter is documented in the schema for `limit`.

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 coverage is 100% with 7 enums fully documented, so the schema does the heavy lifting and baseline 3 applies. The description adds only two marginal points (comma-separated multi-value filters and discovering values via browse/filters) that the per-parameter descriptions largely repeat.

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 movie rows from Rotten Tomatoes' browse listing,' which is clearer than the bare name. It does not, however, distinguish itself from the close siblings rottentomatoes_movies and rottentomatoes_browse_tv, so an agent must still infer which listing tool to pick.

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?

Gives concrete operating context: use `/rottentomatoes/browse/filters` to discover valid values per list, and page with the `after` cursor from the previous response. No explicit when-not or comparison against rottentomatoes_movies/browse_tv, so it stops short of full routing guidance.

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