Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rottentomatoes_browse_tv

Browse TV series listings from Rotten Tomatoes with filters for genre, rating, critics, audience, and streaming services; use cursor pagination to fetch additional rows.

Instructions

Rotten Tomatoes TV discovery rows. Returns TV series rows from Rotten Tomatoes' browse listing. Use /rottentomatoes/browse/filters?list=tv_series_browse to discover current filters; pagination uses the opaque after cursor from the previous response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listNoTV browse list: tv_series_browse
sortNoSort value from browse/filters
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": [
+    "upright",
+    "spilled"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / critics
      Added value: +{
+  "description": "Comma-separated Tomatometer values from browse/filters",
+  "enum": [
+    "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: +[
+  "tv_series_browse"
+]
    • addedInput schema / properties / ratings
      Added value: +{
+  "description": "Comma-separated content ratings from browse/filters",
+  "enum": [
+    "tvy",
+    "tvy7",
+    "tvg",
+    "tvpg",
+    "tv14",
+    "tvma"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / sort / description
      Previous value: -"Sort: popular, newest"New value: +"Sort value from browse/filters"
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "popular",
+  "newest",
+  "a_z",
+  "critic_highest",
+  "critic_lowest",
+  "audience_highest",
+  "audience_lowest"
+]
  2. Addedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the load; it discloses pagination via an opaque `after` cursor and points at a filter-discovery endpoint, which are real behavioral facts. It does not state that this is a read-only listing, whether results are capped or cached, or what the returned rows contain beyond 'TV series rows'.

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?

Two sentences, front-loaded with the return type and followed by the two operational details an agent actually needs. No filler or redundant restatement of the title.

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?

For a 9-parameter browse endpoint with no annotations and no output schema, the description covers pagination and filter discovery adequately. However, with no output schema present, it does not describe what a returned row contains, so the agent cannot anticipate the response shape.

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%, so each parameter is already documented, including enums sourced from browse/filters and the cursor source path. The description restates the filter-discovery and cursor mechanics rather than adding syntax or semantics beyond the schema.

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?

The description states a specific verb and resource ('Returns TV series rows from Rotten Tomatoes' browse listing'), which clearly separates it from movie browsing and title-level siblings. It stops short of naming rottentomatoes_browse_movies or rottentomatoes_search explicitly as the alternative.

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?

It explains the filter-discovery prerequisite via `/rottentomatoes/browse/filters?list=tv_series_browse` and how to paginate, which is genuinely useful usage guidance. It never says when an agent should prefer this over a search or title-lookup sibling, leaving that boundary implicit.

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