Skip to main content
Glama
retracn

automationnation-mcp

by retracn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Google Hotels search

search_hotels
Read-only

Find hotels on Google Hotels by city, neighborhood, or landmark, with dates, price, rating, and star filters, returning nightly and total costs, reviews, and booking links.

Instructions

Search Google Hotels for a city, neighbourhood or landmark. Returns hotel name, star class, guest rating and review count, nightly price with and without taxes, estimated total for the stay, description, nearby places, website, coordinates and Google Hotels link. Set check_in and check_out for exact prices (otherwise Google picks dates). Filter by minimum rating, minimum stars and maximum nightly price. Up to 20 hotels per search, typically 5–20 seconds. Cost on your Apify account: $1 per 1,000 hotels ($0.80 on Gold and above).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adultsNoGuests per room.
countryNoTwo-letter country code for Google, e.g. us, gb, de. It can change the currency and booking partners.us
check_inNoCheck-in date, YYYY-MM-DD.
currencyNoThree-letter currency code (USD, EUR, GBP). Google may still answer in the country's currency.
locationYesWhere to stay: a city (Paris), an area (Shoreditch London) or a full search (hotels near Times Square).
check_outNoCheck-out date, YYYY-MM-DD.
min_starsNoOnly hotels with at least this many stars.any
min_ratingNoOnly hotels with at least this guest rating.any
max_resultsNoHow many hotels to return, 1–20. Each result is billed, so ask for what you need.
max_price_per_nightNoOnly hotels at or under this nightly price, in the results' currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, openWorld, non-destructive, non-idempotent); the description adds the operationally important traits: 20-hotel cap, 5–20 second latency, per-result billing at $1/1,000 hotels, and the non-obvious behavior that omitting dates makes Google choose them. That is substantial disclosure beyond structured fields.

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?

Front-loaded with purpose and scope, then return fields, then date/filter guidance, then limits and cost. Every sentence carries information an agent needs; nothing is restated from the schema or title.

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?

With no output schema, the description compensates by enumerating the return payload (name, star class, rating, review counts, prices with/without taxes, total, description, nearby places, website, coordinates, link). Combined with per-result billing and latency, an agent has everything needed to call and interpret this tool.

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%, so the baseline is 3, but the description adds real meaning: the check_in/check_out pairing determines whether prices are exact or Google-chosen, and the filters are framed as narrowing criteria. It does not clarify the currency-vs-country interaction, which stays in the schema.

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?

States a specific verb and resource (Search Google Hotels) plus the supported location granularity (city, neighbourhood, landmark), and enumerates the returned fields. This clearly distinguishes it from siblings like search_google_shopping or find_local_businesses, which target different resources.

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?

Gives concrete usage context: set check_in/check_out for exact prices, otherwise Google picks dates; how to filter by rating, stars and max nightly price. It does not name an alternative tool or state when NOT to use this one (e.g. vs. find_local_businesses for non-hotel lodging), so it stops short of a full routing rule.

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

Deploy Server

Other Tools