Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

rottentomatoes_browse_tv

Browse Rotten Tomatoes TV series listings with filters for genre, rating, critics, audience, and streaming service, using cursor pagination to retrieve sorted discovery 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.

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

Input Schema

Name	Required	Description
`list`	No	TV browse list: tv_series_browse
`sort`	No	Sort value from browse/filters
`after`	No	Opaque next-page cursor returned in data.page_info.end_cursor
`limit`	No	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
`genres`	No	Comma-separated genre values from browse/filters
`critics`	No	Comma-separated Tomatometer values from browse/filters
`ratings`	No	Comma-separated content ratings from browse/filters
`audience`	No	Comma-separated Popcornmeter values from browse/filters
`affiliates`	No	Comma-separated streaming/service values from browse/filters

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.17.18Nov 2, 2026

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"

Changed10 schema fields changedv1.17.5Sep 26, 2026

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"
+]

Addedv1.1.0Jun 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose pagination behavior and implicitly that this is a read-only listing, but says nothing about auth, rate limits, or what a 'row' contains. For a no-annotation tool this leaves real gaps, though the operation is a simple read.

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?

Three tight sentences with the resource stated first and the practical filter/pagination notes following. Minor awkwardness: it references the filters capability as a path ('/rottentomatoes/browse/filters') rather than the sibling tool name rottentomatoes_browse_filters.

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?

Nine optional parameters are all documented in the schema, and the description covers the two non-obvious behaviors an agent would otherwise get wrong: sourcing filter values and paging with `after`. No output schema exists, and the description gives only a one-line hint at return shape, but that is a minor gap.

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% with 7 enums fully enumerated, so the schema already documents every parameter including the `after` cursor and the limit/page-size interplay. The description restates cursor semantics but adds no syntax or format detail beyond what the schema provides; baseline 3 applies.

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 TV series rows from Rotten Tomatoes' browse listing, and labels the tool as a TV discovery feed. The TV scope distinguishes it by name from rottentomatoes_browse_movies, though it doesn't explicitly contrast with rottentomatoes_search or rottentomatoes_series.

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 prerequisite guidance: discover current filter values via the browse/filters endpoint for list=tv_series_browse before calling. Also explains pagination flow (reuse the opaque `after` cursor from the previous response). No explicit when-not-to-use or comparison against search/series siblings.

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

Deploy Server