Skip to main content
Glama

Search Hotels

search_hotels
Read-onlyIdempotent

Search hotels by city or property, filtering by dates, price, star class, amenities, brands, guest rating, free cancellation, eco-certification, and more. Returns list with pricing, ratings, and key details for quick comparison.

Instructions

Fast list-view hotel search. USE THIS FIRST to discover hotels.

Returns name, price, rating, star class, amenities, check-in/out times, and an entity_key for each hotel. Prefer this over search_hotels_with_details unless the user explicitly asks for room/rate/cancellation detail. One RPC. entity_key values here are inputs to get_hotel_details.

Common filter triggers:

  • 'free cancellation' / 'refundable' → free_cancellation=True

  • 'budget' / 'cheap' → sort_by='LOWEST_PRICE' or price_max=N

  • 'luxury' / '5-star' → hotel_class=[5]

  • 'family' / 'kid-friendly' → amenities=['KID_FRIENDLY']

  • 'pet-friendly' / 'dogs allowed' → amenities=['PET_FRIENDLY']

  • 'pool' → amenities=['POOL'] or ['INDOOR_POOL'] or ['OUTDOOR_POOL']

  • 'wheelchair' / 'accessible' → amenities=['WHEELCHAIR_ACCESSIBLE']

  • 'eco' / 'sustainable' → eco_certified=True

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesCity or property query, e.g. 'hotels in Paris' or 'Hilton Tokyo'.
check_inNoCheck-in date YYYY-MM-DD. Omit for flexible dates.
check_outNoCheck-out date YYYY-MM-DD. Required when check_in is set.
adultsNoNumber of adult guests.
childrenNoNumber of children. Provide child_ages when > 0.
child_agesNoOne age (0-17) per child.
currencyNoISO 4217 currency code, e.g. 'USD', 'EUR', 'GBP'.USD
sort_byNoSort order: RELEVANCE (default), LOWEST_PRICE, HIGHEST_RATING, MOST_REVIEWED.RELEVANCE
hotel_classNoStar classes to include, e.g. [4, 5] for luxury. Each value 1-5.
amenitiesNoAmenity filter names, e.g. ['WIFI', 'POOL', 'GYM', 'SPA', 'PARKING', 'BREAKFAST', 'PET_FRIENDLY'].
brandsNoBrand family filters, e.g. ['HILTON', 'MARRIOTT', 'HYATT', 'IHG', 'ACCOR'].
min_guest_ratingNoMinimum guest rating. Use 3.5, 4.0, or 4.5.
free_cancellationNoOnly show hotels with free cancellation. Use when the user asks for 'refundable', 'flexible booking', 'cancel anytime', or 'free cancellation'.
eco_certifiedNoFilter to Google eco-certified properties only.
special_offersNoOnly show hotels with current deals or member rates.
price_minNoMinimum per-night price in the selected currency.
price_maxNoMaximum per-night price in the selected currency.
property_typeNoHOTELS (default) or VACATION_RENTALS.HOTELS
max_resultsNoCap the number of hotels returned. Omit to return all Google surfaces (typically 15-18).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint. The description adds value by mentioning performance ('Fast', 'One RPC'), returning specific fields including entity_key for chaining, and explaining entity_key usage in get_hotel_details.

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 well-structured with a clear first paragraph on purpose and output, followed by a list of filter triggers. It is front-loaded with the key instruction. Slightly long but every sentence adds value; could be tightened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool complexity (19 parameters, 100% schema coverage, output schema present), the description is highly complete. It covers purpose, usage guidelines, output fields, and parameter semantics without leaving major gaps.

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 description coverage is 100%, baseline is 3. However, the description adds substantial value by mapping user phrases to parameters (e.g., 'free cancellation' → free_cancellation=True, 'luxury' → hotel_class=[5]), significantly aiding parameter selection beyond schema descriptions.

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 it's a 'Fast list-view hotel search' and instructs to 'USE THIS FIRST to discover hotels.' It distinguishes itself from siblings by noting that 'Prefer this over search_hotels_with_details unless the user explicitly asks for room/rate/cancellation detail.'

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?

Explicitly provides when to use ('USE THIS FIRST') and when not to use (use search_hotels_with_details for details). Also includes a comprehensive list of common filter triggers mapping natural language to parameters.

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/him229/stays'

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