Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opentable_restaurant_reviews

Retrieve paginated diner reviews for an OpenTable restaurant by ID, including ratings for food, service, ambience, and value plus reviewer details and recommendation flags.

Instructions

Get a page of an OpenTable restaurant's diner reviews. Returns one page of diner reviews for an OpenTable restaurant, identified by the required restaurant_id. page defaults to 1 and size to 20. Each review has its id, author and author's metro area, reservation and posted dates, text, a recommended flag, and ratings for overall, food, service, ambience, value and noise.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, default 1
sizeNoReviews per page, default 20
restaurant_idYesOpenTable restaurant id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses pagination defaults, the required identifier, and the return fields, which is useful context. However, it omits authentication needs, rate limits, sorting order, or pagination limits, leaving clear gaps for a read tool with no annotation coverage.

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 front-loaded with the core purpose and efficiently lists pagination defaults and return fields. It contains minor redundancy between the first two sentences ('Get a page...' and 'Returns one page...'), but no sentence is wasted.

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?

For a simple paginated list tool with no output schema and no annotations, the description covers the required identifier, defaults, and the shape of each returned review. It is nearly complete, though it could mention sorting or maximum page sizes to be fully self-contained.

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 documented. The description repeats the same defaults (page=1, size=20) and required restaurant_id without adding syntax, constraints, or meaning beyond what the schema provides, making the baseline 3 appropriate.

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 ('Get a page of') and resource ('OpenTable restaurant's diner reviews'), making the tool's intent immediately clear. However, it does not explicitly differentiate itself from sibling tools like opentable_restaurant or opentable_restaurant_menus, so it falls short of a full 5.

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

Usage Guidelines2/5

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

The description offers no explicit when-to-use guidance, prerequisites, or alternatives (e.g., when to choose this over opentable_restaurant or other review sources). Usage is only implied by the purpose statement, which is insufficient for a 3.

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