Skip to main content
Glama

Searchapi

by io.searchapi
OverviewDiscussionsAdmin

Google Hotels

google_hotels
Read-only

Search for hotels using Google Hotels. Provides pricing, ratings, amenities, and availability for hotels, resorts, inns, motels, and other traditional accommodations worldwide.

Required: q (destination), check_in_date, check_out_date (both YYYY-MM-DD). Use sort_by="lowest_price" for cheapest results. Supply children_ages as a string, e.g. "5,10".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query for hotel location (e.g., 'Hotels in Manhattan New York'). Required.
glNoISO 3166-1 alpha-2 country code in lowercase (e.g., 'us', 'gb', 'de'). Affects pricing and availability. Default: us.
hlNoLanguage code for results (e.g., 'en', 'es'). Default: en.
adultsNoNumber of adults as an integer, e.g. 2 (1-6). Default: 2. Total guests (adults + children) cannot exceed 6.
brandsNoComma-separated brand IDs to filter by. Brand IDs can be found in search results.
ratingNoMinimum rating filter: 7 for 3.5+ stars, 8 for 4.0+ stars, 9 for 4.5+ stars.
sort_byNoSort order for results: relevance, lowest_price, highest_rating, most_reviewed. Use the text label (e.g. 'highest_rating'), not a numeric code. Default: relevance.
currencyNoCurrency code for prices (e.g., 'USD', 'EUR'). Default: USD.
amenitiesNoComma-separated amenity names: free_parking, parking, indoor_pool, outdoor_pool, pool, fitness_centre, restaurant, free_breakfast, spa, beach_access, kid_friendly, bar, pet_friendly, room_service, free_wi_fi, air_conditioned, all_inclusive_available, wheelchair_accessible, ev_charger
price_maxNoMaximum price filter in the specified currency.
price_minNoMinimum price filter in the specified currency.
hotel_classNoComma-separated hotel star ratings to filter by (e.g., '3,4,5' for 3-star and above). Values: 2, 3, 4, 5.
check_in_dateYesCheck-in date in YYYY-MM-DD format. Required.
children_agesNoComma-separated string of ages of children 1-17 (e.g., '5,10'). Maximum 5 children. Total guests cannot exceed 6.
eco_certifiedNoFilter for eco-certified properties.
check_out_dateYesCheck-out date in YYYY-MM-DD format. Required.
property_typesNoComma-separated property types: beach_hotels, boutique_hotels, hostels, inns, motels, resorts, spa_hotels, bed_and_breakfasts, other, apartment_hotels, minshuku, japanese_style_business_hotels, ryokan
special_offersNoFilter for properties with special offers or deals.
next_page_tokenNoToken for paginating to the next page of results. Found in previous search results.
free_cancellationNoFilter for properties with free cancellation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / children_ages / description
      Previous value: -"Comma-separated ages of children 1-17 (e.g., '5,10'). Maximum 5 children. Total guests cannot exceed 6."New value: +"Comma-separated string of ages of children 1-17 (e.g., '5,10'). Maximum 5 children. Total guests cannot exceed 6."
  2. Changed2 schema fields changed
    • changedInput schema / properties / adults / description
      Previous value: -"Number of adults (1-6). Default: 2. Total guests (adults + children) cannot exceed 6."New value: +"Number of adults as an integer, e.g. 2 (1-6). Default: 2. Total guests (adults + children) cannot exceed 6."
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort order for results. Default: relevance."New value: +"Sort order for results: relevance, lowest_price, highest_rating, most_reviewed. Use the text label (e.g. 'highest_rating'), not a numeric code. Default: relevance."
  3. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed6 schema fields changed
    • removedInput schema / properties / eco_certified / enum
      Removed value: -[
-  "true",
-  "false"
-]
    • changedInput schema / properties / eco_certified / type
      Previous value: -"string"New value: +[
+  "boolean",
+  "string"
+]
    • removedInput schema / properties / free_cancellation / enum
      Removed value: -[
-  "true",
-  "false"
-]
    • changedInput schema / properties / free_cancellation / type
      Previous value: -"string"New value: +[
+  "boolean",
+  "string"
+]
    • removedInput schema / properties / special_offers / enum
      Removed value: -[
-  "true",
-  "false"
-]
    • changedInput schema / properties / special_offers / type
      Previous value: -"string"New value: +[
+  "boolean",
+  "string"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / gl / description
      Previous value: -"Country code for search context (e.g., 'us', 'gb'). Default: us."New value: +"ISO 3166-1 alpha-2 country code in lowercase (e.g., 'us', 'gb', 'de'). Affects pricing and availability. Default: us."
  6. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and external-data aspects. The description adds the scope (worldwide) and the requirement of date parameters, but does not disclose any additional behavioral nuances (e.g., pagination via next_page_token or result variability). Since annotations carry the main burden, a 3 is appropriate.

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 extremely concise: two sentences plus a compact list of required fields and two usage tips. It front-loads the primary purpose and avoids fluff, earning its place with no waste.

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 20 parameters and no output schema, the description effectively highlights the essentials (required params and key tips) while relying on the comprehensive schema for the rest. It lacks a full example of a typical call, but the schema plus description covers what an agent needs to make a valid request. A 4 reflects a near-complete 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 coverage is 100%, so all parameters are documented. The description adds a few usage pointers (sort_by='lowest_price', children_ages format) that reinforce but do not extend beyond the schema's own descriptions. Baseline 3 applies when schema is complete and the description adds only marginal clarification.

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 a specific action ('Search for hotels') and a specific resource ('Google Hotels'), and specifies what it provides (pricing, ratings, amenities, availability). It distinguishes itself from sibling search tools like google_flights_* or google_maps_search by being explicitly about traditional hotel accommodations worldwide.

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?

It explicitly lists the required parameters (q, check_in_date, check_out_date) and provides a practical hint for using sort_by='lowest_price' and formatting children_ages. However, it does not explicitly compare to alternatives like google_vacation_rentals or state when not to use this tool, though the hotel-specific focus makes the context clear.

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

All Searchapi toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources