Skip to main content
Glama

Booking.com guest reviews featured on a city page: hotel

travel_booking_com_reviews
Read-only

Booking.com guest reviews featured on a city page (e.g. us / new-york): hotel reviews with hotel name, hotel guest score and review count, reviewer name, country and traveller type; guests' reviews of the city itself (score out of 10); and the highlighted review of each top hotel. Typically 10-25 reviews in total; it is the selection Booking.com shows on the city page, not a hotel's full review history. Related tools on this server, for a different need: travel_booking_com_hotels when you need hotels featured on a Booking.com city page: name, property; travel_booking_com when you need Booking.com hotel price guide for a city: the lowest 'from'. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>",
      "city": "<city>"
    },
    "name": "travel_booking_com_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity as in Booking.com city URLs, e.g. new-york, paris, barcelona
countryYesTwo-letter country code as in Booking.com city URLs, e.g. us, fr, gb

Output Schema

NameRequiredDescriptionDefault
cityNo
countsNo
sourceNo
countryNo
checkedAtNo
cityReviewsNo
highlightedNo
hotelReviewsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely non-obvious behavior: the result is a bounded selection (typically 10-25 reviews) rather than a full corpus, and calls cost $0.002 via x402 (USDC on Base, Solana and 10 more networks) with failed calls not charged — material facts an agent cannot get from structured fields. It stops short of describing pagination or coverage guarantees, which keeps it at a 4 rather than 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.

Conciseness4/5

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

Content is front-loaded: what the data is, then how much, then the scope caveat, then alternatives, then price. Every segment carries information. The main flaw is density — a long semicolon-chained sentence plus a compressed trailing price clause makes it heavier to parse than necessary.

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 an output schema present, the description does not need to explain return shapes, and annotations cover the read-only profile. It still discloses result volume, scope limits, sibling routing and pricing, which is complete for a 2-parameter read tool. The only gap is no mention of error behavior for invalid city/country inputs, a minor omission given a 100%-covered schema.

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 schema already explains both parameters, including the URL-form city and two-letter country conventions. The description's own 'us / new-york' example mirrors the schema rather than adding new meaning. Baseline 3 is appropriate.

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?

The description names the exact resource (Booking.com guest reviews on a city page), the concrete payload (hotel name, guest score, review count, reviewer name, country, traveller type, city scores, highlighted review), and the scope boundary ('it is the selection Booking.com shows on the city page, not a hotel's full review history'). It also differentiates itself from travel_booking_com_hotels and travel_booking_com by their distinct return values. An agent can distinguish this tool from every named sibling 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?

It explicitly routes: use this for the city-page review selection, use travel_booking_com_hotels for city-page hotel listings, and travel_booking_com for a price guide ('the lowest from'). It also carries an implicit exclusion ('not a hotel's full review history'), which tells the agent when this tool will under-deliver. Alternative routing plus scope exclusion is exactly what usage guidance should provide.

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.

Resources