Skip to main content
Glama
HasData

HasData MCP Server

Official

google_travel_hotels: GET /

hasdata_google_travel_hotels_getGoogleHotels

Search Google Hotels for hotels and vacation rentals by dates, guests, location, and filters like price, rating, amenities, and property type. Returns structured rates, reviews, and property details.

Instructions

Get Google Hotels Results

Searches Google Hotels for hotels and vacation rentals with check-in/check-out dates, guest mix (adults, children with ages), localization (domain, country, language, currency), and advanced filters: price range, property types, amenities, minimum rating, brands, hotel class, free cancellation, special offers, eco-certified, vacation rentals only, bedrooms, bathrooms, and sort order (lowest price, highest rating, most reviewed). Returns per-property name, description, link, GPS coordinates, check-in/out times, rate per night and total rate, price comparisons across sources, hotel class, overall rating, reviews, location rating, images, amenities, nearby places, deals, eco-certification, and pagination tokens. Use for travel research agents, hotel rate monitoring, OTA dashboards, and competitive analysis of accommodations across markets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesThe search query for Google Hotels (e.g., a city, neighborhood, or hotel name).
glNoThe two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`.
hlNoThe two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`.
adultsNoNumber of adult guests (1-6).
brandsNoComma-separated list of brand IDs to filter by. Brand IDs are returned in the response under `brands` for the same query.
ratingNoFilter by minimum overall guest rating. Options: - `threePointFivePlus` — 3.5 stars or higher - `fourPlus` — 4.0 stars or higher - `fourPointFivePlus` — 4.5 stars or higher
sortByNoSort hotel results. Options: - `lowestPrice` — lowest price - `highestRating` — highest rating - `mostReviewed` — most reviewed
bedroomsNoMinimum number of bedrooms (vacation rentals only).
childrenNoNumber of child guests (1-5). Total guests (adults + children) cannot exceed 6.
currencyNoParameter defines the currency of the returned prices Provide one exact documented value (71 allowed), e.g. `ALL`, `DZD`.
maxPriceNoMaximum price per night, in the selected currency.
minPriceNoMinimum price per night, in the selected currency.
amenity__NoList of amenities to filter by (e.g., `hotelFreeWifi,hotelPool`). Values prefixed `hotel*` apply when searching hotels (the default mode). Values prefixed `rental*` apply when `vacationRentals=true`. The two sets are disjoint because Google Hotels exposes different amenity catalogs for each mode — pass values matching the mode you're querying.
bathroomsNoMinimum number of bathrooms (vacation rentals only).
hotelClassNoComma-separated list of hotel star classes to include (e.g., `2,3,4,5`).
checkInDateYesThe check-in date in 'yyyy-MM-dd' format.
checkOutDateYesThe check-out date in 'yyyy-MM-dd' format.
childrenAgesNoComma-separated list of children ages (e.g., `5,8,12`). Must match the number of children.
ecoCertifiedNoShow only eco-certified properties.
nextPageTokenNoToken to fetch the next page of hotel results. Returned in the `pagination` field of a previous response.
propertyTokenNoToken used to retrieve details for a specific property. Returned in each property in the results.
specialOffersNoShow only properties with special offers.
propertyType__NoList of property types to filter by (e.g., `hotelResort,hotelMotel`). Values prefixed `hotel*` apply when searching hotels (the default mode). Values prefixed `rental*` apply when `vacationRentals=true`. The two sets are disjoint because Google Hotels exposes different property-type catalogs for each mode — pass values matching the mode you're querying.
vacationRentalsNoSearch vacation rentals instead of hotels.
freeCancellationNoShow only properties offering free cancellation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.2

TDQS

A4.6/5.0
Behavior4/5

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

No annotations were provided (no read-only or destructive hints), so the description carries the full burden. The description thoroughly explains what the tool does and returns, and as a search tool it is implicitly non-destructive. It doesn't mention rate limits or auth, but nothing contradicts the (absent) annotations, so no contradiction flag.

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 a single dense paragraph followed by use cases — reasonably structured and free of filler. It's long, but the density of useful information (explicit use cases, return scope) justifies the length without becoming wordy.

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?

There is no output schema, so the description doesn't need to detail return values. It compensates by explaining the data model through parameter docs (brands, pagination, property tokens) and by stating the range of returned per-property fields. Adequate for an agent to invoke the tool correctly.

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

Parameters5/5

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

Schema coverage is 100%, and the descriptions add substantial value beyond the raw types: enum options (rating, sortBy) are human-readable, amenities and propertyType explain the disjoint hotel vs rental catalogs, childrenAges explains the count-matching requirement, and nextPageToken/propertyToken explain where the tokens originate. This far exceeds baseline expectation.

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 clearly states the tool's purpose — searching Google Hotels for hotels and vacation rentals with dates, guest mix, localization, and filters. It distinguishes itself from sibling tools (e.g., Google Flights, Airbnb, Booking) by being specifically for Google Hotels data, and explicitly names its use cases.

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?

The description explicitly lists when to use this tool — travel research agents, hotel rate monitoring, OTA dashboards, and competitive analysis. Combined with the sibling-tool list (Google Flights, Airbnb, Booking, etc.), it clearly routes the agent to the right tool without ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools