Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

booking_attractions_reviews

Retrieve guest reviews for a Booking.com attraction using its product ID. Specify page and limit to collect review scores, comments, reviewer details, and dates.

Instructions

Booking.com attraction reviews. Returns guest reviews for a Booking.com attraction. product_id is required and comes from products[].id in a booking-attractions-search result. page is 1-based (default 1) and limit is 1 to 50 (default 10). Each review has score, content, reviewer_name, reviewer_country, language and reviewed_date, and total gives the count.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based result page, default 1
limitNoReviews per page, 1-50, default 10
product_idYesAttraction product id, from a prior attraction search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/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, and it does disclose the return shape (score, content, reviewer_name, reviewer_country, language, reviewed_date) plus that 'total' gives the count, and it covers pagination. It does not mention auth or rate-limit behavior, keeping it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the purpose, then the required id and its source, then pagination, then return fields. Zero padding; every clause conveys actionable information.

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?

With no output schema and no annotations for a 3-param tool, the description supplies the missing return-value detail (review fields and total count). It is essentially complete for calling the tool correctly, though it could note anything about ordering or empty-result behavior.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by pinpointing the exact origin of product_id ('products[].id in a booking-attractions-search result') and restating the 1-based page and 1–50 limit bounds, giving the agent more routing context than the schema alone.

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 guest reviews for a Booking.com attraction.' An agent can tell it apart from booking_attractions_search/detail by the 'reviews' resource. It does not explicitly name a sibling to disambiguate against, so it stops short of a 5.

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 clear prerequisite context: product_id 'is required and comes from products[].id in a booking-attractions-search result', establishing the intended call sequence. No explicit when-not or alternative selection guidance, so not a 5.

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