Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_browse_movies

Browse Rotten Tomatoes movie lists and filter by genre, rating, critic scores, streaming service, and more to retrieve structured movie discovery data.

Instructions

Rotten Tomatoes movie discovery rows. Returns normalized movie rows from Rotten Tomatoes' public browse JSON route. 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

TableJSON 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 10, max 30
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. 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"
+]
  2. Addedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral disclosure burden. It reveals that the data comes from a public JSON route, results are normalized rows, filter parameters accept comma-separated values, and pagination relies on an opaque after cursor rather than page numbers. It does not specify return fields or auth/rate-limit behavior, but the core mechanics of a read-only browse tool are well covered.

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?

The description is compact and front-loads the tool's purpose before moving to workflow details. The first fragment and the second sentence overlap on "movie rows," but there is no filler or irrelevant content.

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?

The schema covers all 9 parameters with enums and descriptions, and the description explains the browse/filters prerequisite and pagination cursor. However, with no output schema and no annotations, "normalized movie rows" is vague about the actual return shape, and the description does not clarify behavior when no parameters are supplied despite required being empty.

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 parameters are already thoroughly documented. The description adds cross-cutting workflow context—filters take comma-separated values and the after cursor comes from the previous response—but it does not add per-parameter meaning beyond what the schema already states.

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?

The description uses a specific verb and resource: "Returns normalized movie rows from Rotten Tomatoes' public browse JSON route." The explicit "movie rows" wording distinguishes this tool from the sibling rottentomatoes_browse_tv and aligns with the tool name.

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?

It gives a clear, actionable usage rule: call /rottentomatoes/browse/filters to discover current values for each list. It does not enumerate when-not-to-use cases or explicitly contrast with alternatives, but the context is clear enough for an agent to know the prerequisite step.

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