Skip to main content
Glama

google_hotels

Retrieves Google Hotels search results including property listings, pricing, ratings, and amenities. Supports filters like dates, price range, rating, and property type, with pagination and detailed property info.

Instructions

Retrieves Google Hotels search results including property listings, pricing, ratings, amenities, and detailed property info (via property_token). Costs 5 API credits per request. [Credits: 5 API credits per request] Notes: check_in_date/check_out_date use YYYY-MM-DD. Several hotel-only filters (brands, hotel_class, free_cancellation, special_offers, eco_certified) are not supported when vacation_rentals=true; conversely bedrooms/bathrooms only apply when vacation_rentals=true. Pagination via next_page_token; use property_token for a detail lookup on a single property. Returns: { ads: [{title, source, price, reviews, overall_rating, amenities: [], hotel_class, free_cancellation}] } (sample truncated in docs; likely also includes a properties/hotels results array alongside ads)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlNoReturn the full HTML of the Google page. (default: false)
queryYesSearch query, anything you would normally type into a standard Google Hotels search.
adultsNoNumber of adults. (default: 2)
brandsNoBrand ID(s) to focus the search on. Single: '33'; multiple: '33,67,101'. Not supported for Vacation Rentals.
ratingNoMinimum rating filter. Allowed values: 7 (3.5+), 8 (4.0+), 9 (4.5+).
countryNoTwo-letter country code for the Google search (e.g. US, UK, FR). (default: us)
sort_byNoSort order. Default is Relevance. Allowed values: 3 (lowest price), 8 (highest rating), 13 (most reviews).
bedroomsNoMinimum number of bedrooms. Vacation Rentals only. (default: false)
childrenNoNumber of children. (default: 0)
currencyNoCurrency for returned prices. (default: USD)
languageNoLanguage of the results, e.g. en, es, fr, de. (default: en)
amenitiesNoOnly include listings with the selected amenities; see the Google Hotels / Vacation Rentals Amenities reference pages for allowed values.
bathroomsNoMinimum number of bathrooms. Vacation Rentals only. (default: false)
max_priceNoMaximum price in the results range.
min_priceNoMinimum price in the results range.
hotel_classNoFilter to specific star ratings. Allowed values: 2, 3, 4, 5. Not supported for Vacation Rentals.
check_in_dateYesCheck-in date, format YYYY-MM-DD, e.g. 2025-08-15.
children_agesNoAges of children, valid range 1-17. Single child: '5'; multiple: '5,8,10'.
eco_certifiedNoOnly include eco-certified listings. Not supported for Vacation Rentals.
check_out_dateYesCheck-out date, format YYYY-MM-DD, e.g. 2025-08-16.
property_tokenNoRetrieves detailed property information (name, address, phone number, prices, nearby places, etc.) for a specific property.
property_typesNoProperty type(s) to include; see the Google Hotels / Vacation Rentals Property Types reference pages for allowed values.
special_offersNoOnly include listings with special offers. Not available for Vacation Rentals.
next_page_tokenNoToken to fetch the next page of results.
vacation_rentalsNoSearch Vacation Rentals instead of Hotels. (default: false)
free_cancellationNoOnly include listings offering free cancellation. Not available for Vacation Rentals.
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: credit cost (5 API credits), date format (YYYY-MM-DD), filter mutual exclusivity between hotels and vacation rentals, pagination via next_page_token, and detail lookup via property_token. Example return structure is also included.

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?

The description is a single efficient paragraph front-loaded with purpose, then credit cost, then parameter constraints, then pagination, then return structure. Every sentence adds value with no redundancy.

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?

Given 26 parameters, 3 required, no output schema, the description covers core flows (search and detail lookup), filter constraints, pagination, and sample output. Could be enhanced with rate limit info, but overall adequate for agent understanding.

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% with parameter descriptions. The description adds context beyond schema: mutual exclusivity of certain filters, credit cost, pagination mechanism, and property_token usage. This justifies a score above the baseline of 3.

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?

Description clearly states the tool retrieves Google Hotels search results including property listings, pricing, ratings, amenities, and detailed property info via property_token. The verb 'retrieves' and specific resource 'Google Hotels search results' make the purpose unambiguous and distinguishable from siblings like google_search or google_flights.

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?

Description provides usage guidelines like credit cost, date format, and filter compatibility notes (e.g., hotels filters not supported for vacation rentals). It explains pagination and property token usage. However, it does not explicitly contrast with alternative tools like google_search for general hotel queries.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alessandrobenigni/ScrapingDog-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server