Skip to main content
Glama
Sign In
Google Hotels MCP

Google Hotels MCP

by huynhtanan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour Apify Personal API token from https://console.apify.com/account/integrations

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_hotelsA

Search Google Hotels for a destination between two dates.

Returns a JSON array of hotels with name, rating, review count, price per night, total price, hotel class, address, coordinates, amenities, hero photo and the Google /travel/hotels/entity URL. When include_provider_prices is true each hotel also gets a providers list with the rate every booking site (Booking.com, Expedia, Agoda, Vrbo, Hotels.com, ...) is charging for the stay (one extra Apify provider-prices call per hotel, billed per-hotel).

Args: query: destination, e.g. "hotels in Paris" or "Hilton near Louvre". check_in: ISO date YYYY-MM-DD. check_out: ISO date YYYY-MM-DD. adults: number of adults. children: number of children. rooms: number of rooms. currency: ISO 4217 code (USD, EUR, GBP, ...). hl: Google interface language (en, fr, de, ...). gl: Google country code (us, gb, fr, ...). max_results: upper bound on hotels returned. min_rating: filter to hotels at or above this guest rating (0-5). min_hotel_class: filter to hotels at or above this class (2-5). include_provider_prices: fetch per-provider rates. Each hotel priced this way adds one provider-prices call to the Apify bill. Defaults to false to keep costs predictable.

hotel_price_calendarA

Return a daily rate calendar for one Google Hotels property.

By default this returns 90 forward dates (roughly three months), one row per date. Each item has date, price, currency and available.

Args: hotel_url: a Google /travel/hotels/entity/<token> URL. start_date: ISO date YYYY-MM-DD where the calendar starts. number_of_dates: how many forward dates to price (default 90 = 3 months). nights: stay length to price per date (1 = per-night rate). currency: ISO 4217 code. hl: Google interface language. gl: Google country code. adults: number of adults for the stay. children: number of children. rooms: number of rooms.

search_vacation_rentalsA

Search Google Vacation Rentals (Airbnb / Vrbo / Booking.com) for a stay.

Returns a JSON array of rentals with title, nightly price, total price, rating, review count, bedrooms, bathrooms, amenities, hero photo and the Google /travel/vacation-rentals/entity URL. When include_provider_prices is true each rental also gets a providers list with the price every listing site (Airbnb, Vrbo, Booking.com) is charging (one extra provider-prices call per rental, billed per-rental).

Args: query: destination, e.g. "vacation rentals in Lisbon". check_in: ISO date YYYY-MM-DD. check_out: ISO date YYYY-MM-DD. adults: number of adults. children: number of children. currency: ISO 4217 code. hl: Google interface language. gl: Google country code. max_results: upper bound on rentals returned. include_provider_prices: fetch per-provider rates. Each rental priced this way adds one provider-prices call to the Apify bill. Defaults to false to keep costs predictable.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation4/5

search_hotels and search_vacation_rentals are distinguished by resource type (hotels vs vacation rentals), which descriptions make clear, but the boundary could be blurry for a query like 'apartments in Lisbon'. hotel_price_calendar is clearly distinct as a per-property pricing tool.

Naming Consistency4/5

Two tools follow a clean verb_noun pattern (search_hotels, search_vacation_rentals) and all names are snake_case, but hotel_price_calendar deviates to a noun-phrase form, slightly breaking the search_* symmetry an agent might expect.

Tool Count3/5

Three tools is thin for a travel-search server, though each covers a distinct capability. A property-details or reviews tool would round out the surface, so the count sits at the borderline rather than being well-scoped.

Completeness3/5

The set covers hotel search, per-property pricing, and vacation rentals, but there is no tool to fetch full details or reviews for a single hotel, and no equivalent calendar for rentals. Agents can work around this via search results, but notable gaps remain.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources