Google Hotels MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | Your HasData API key from the dashboard (https://app.hasdata.com/sign-up) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| completions | {} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hasdata_google_travel_hotels_getGoogleHotelsA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of overlap or confusion. The tool's purpose is clearly defined in its description, making it unambiguous for an agent.
The single tool name 'hasdata_google_travel_hotels_getGoogleHotels' mixes snake_case (hasdata_google_travel_hotels) with camelCase (getGoogleHotels), creating an inconsistent and verbose pattern. While it is descriptive, it does not follow a clean naming convention.
With only one tool, the server feels thin even though the tool itself is highly comprehensive. A single-purpose server can justify one tool if it fully covers its domain, but the count is at the lower boundary of acceptable.
The tool provides a rich search capability with extensive filters and detailed results, covering the core need of hotel research. There is no separate tool for retrieving individual hotel details, but the search response already includes sufficient data, so no critical gaps are evident.