Skip to main content
Glama

Hotels featured on a Booking.com city page: name, property

travel_booking_com_hotels
Read-only

Hotels featured on a Booking.com city page (e.g. us / new-york): name, property id, sample nightly price as displayed (in the currency you pick), guest score out of 10, review count, stars, district, coordinates, a featured guest review and the hotel URL. Comes from the page's 'top hotels' and 'most booked' blocks (usually 10-15 hotels). Prices are Booking.com's landing-page samples, not a live date search. Related tools on this server, for a different need: travel_booking_com_reviews when you need Booking.com guest reviews featured on a city page: hotel; 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_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity as in Booking.com city URLs, e.g. new-york, paris, london, istanbul
countryYesTwo-letter country code as in Booking.com city URLs, e.g. us, fr, gb, tr
currencyNoThree-letter currency code for prices (default USD)

Output Schema

NameRequiredDescriptionDefault
cityNo
countNo
destIdNo
hotelsNo
regionNo
sourceNo
countryNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds substantial context beyond them: the expected result size (usually 10-15 hotels), the fact that prices are landing-page samples rather than date-specific quotes, and the billing model ($0.002 per successful call via x402, failed calls not charged). The cost and failure-charging disclosure is exactly the kind of operational detail an agent needs before invoking a paid tool.

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 opening sentence is front-loaded with the resource and full field list, followed by source blocks, the pricing caveat, alternatives, and cost. Every element earns its place, though the long comma-delimited field enumeration and the repeated 'when you need' phrasing in the alternatives section make it denser 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 values, yet it still summarizes them helpfully. It covers source, sample size, price semantics, cost and alternatives — enough for a simple read-only, three-parameter tool. Only error behavior for invalid city/country pairs is left unaddressed, a minor gap given schema-level format guidance.

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% and each parameter already documents its format with examples, so the description is not required to carry parameter meaning. It adds only marginal value — clarifying that the displayed price uses 'the currency you pick' — while city/country formatting is left entirely to the schema. 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?

States precisely what is returned — hotels featured on a Booking.com city page with name, property id, sample nightly price, guest score, review count, stars, district, coordinates, featured review and URL. It also names the exact source blocks ('top hotels' and 'most booked'), which tells an agent this is a page-scrape of a landing page rather than a live search, and it distinguishes itself from the two related Booking.com siblings.

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?

The 'Related tools on this server, for a different need' sentence routes the agent to travel_booking_com_reviews for featured guest reviews and travel_booking_com for the lowest 'from' price guide, with a stated condition for each. It also rules out one misuse case ('not a live date search'), though it never explicitly states the situations where this tool itself is the right choice beyond the purpose statement.

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