Skip to main content
Glama

rottentomatoes_browse_movies

Read-only

Browse Rotten Tomatoes movie results by list and filters. Use rottentomatoes_browse_filters for the selected list's valid filters; multi-value filters accept comma-separated values. Resume with after from page_info.end_cursor; limit defaults to 10, capped at 30. Use rottentomatoes_search for a title-name query.

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

Input Schema

NameRequiredDescriptionDefault
listNoMovie browse list: movies_in_theaters, movies_at_home, movies_coming_soon. Documented values: movies_in_theaters, movies_at_home, movies_coming_soon.
sortNoSort value from the selected list's browse/filters response. Documented values: popular, newest, top_box_office, a_z, critic_highest, critic_lowest, audience_highest, audience_lowest.
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. Documented values: 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.
criticsNoComma-separated Tomatometer values from browse/filters. Documented values: certified_fresh, fresh, rotten.
ratingsNoComma-separated content ratings from browse/filters. Documented values: g, pg, pg_13, r, nc_17, nr, ur.
audienceNoComma-separated Popcornmeter values from browse/filters. Documented values: verified_hot, upright, spilled.
affiliatesNoComma-separated streaming/service values from browse/filters. Documented values: theaters, fandango, apple-tv-plus, netflix, prime-video, disney-plus, max, peacock, hulu, paramount-plus, amc-plus, acorn-tv, apple-tv.

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. Changed1 schema field changed
    • 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. Changed9 schema fields changed
    • addedInput schema / properties / affiliates / description
      Added value: +"Comma-separated streaming/service values from browse/filters. Documented values: theaters, fandango, apple-tv-plus, netflix, prime-video, disney-plus, max, peacock, hulu, paramount-plus, amc-plus, acorn-tv, apple-tv."
    • addedInput schema / properties / after / description
      Added value: +"Opaque next-page cursor returned in data.page_info.end_cursor"
    • addedInput schema / properties / audience / description
      Added value: +"Comma-separated Popcornmeter values from browse/filters. Documented values: verified_hot, upright, spilled."
    • addedInput schema / properties / critics / description
      Added value: +"Comma-separated Tomatometer values from browse/filters. Documented values: certified_fresh, fresh, rotten."
    • addedInput schema / properties / genres / description
      Added value: +"Comma-separated genre values from browse/filters. Documented values: 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."
    • addedInput schema / properties / limit / description
      Added value: +"Rows to return, default 10, max 30"
    • addedInput schema / properties / list / description
      Added value: +"Movie browse list: movies_in_theaters, movies_at_home, movies_coming_soon. Documented values: movies_in_theaters, movies_at_home, movies_coming_soon."
    • addedInput schema / properties / ratings / description
      Added value: +"Comma-separated content ratings from browse/filters. Documented values: g, pg, pg_13, r, nc_17, nr, ur."
    • addedInput schema / properties / sort / description
      Added value: +"Sort value from the selected list's browse/filters response. Documented values: popular, newest, top_box_office, a_z, critic_highest, critic_lowest, audience_highest, audience_lowest."
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Adds genuine operational context beyond the readOnly/openWorld annotations: cursor-based paging via page_info.end_cursor and a page-size cap. However, it claims 'limit defaults to 10' while the schema states default 30, so the one behavioral detail it stresses is internally inconsistent and could cause the agent to mis-page.

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 purpose, then prerequisites, then paging, then the alternative. No filler, though the paging sentence spends space on the wrong default value.

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?

With an output schema present, return values needn't be explained, and the filter-discovery and paging story is covered. The one gap is the conflicting limit default, which leaves the agent unsure how to size pages safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description's only added semantics duplicate the schema (comma-separated multi-values are already stated per parameter) and contradict it on the limit default (10 vs 30). Misstating a documented default is worse than adding nothing.

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?

States a specific verb and resource ('Browse Rotten Tomatoes movie results by list and filters') and explicitly separates itself from rottentomatoes_browse_filters and rottentomatoes_search. An agent can pick the right tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use rottentomatoes_browse_filters to discover valid filter values for the chosen list, and rottentomatoes_search for a title-name query. The when-to-use-this vs alternatives question is fully answered.

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.