Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Search hotels and prices on Google Hotels

search_google_hotels
Read-onlyIdempotent

Hotels for a city or place from Google Hotels for your dates: name, hotel class, rating and review count, nightly and total price with and without taxes, the deal versus the usual price, check-in and check-out times and coordinates.

Instructions

Hotels for a city or place from Google Hotels for your dates: name, hotel class, rating and review count, nightly and total price with and without taxes, the deal versus the usual price, check-in and check-out times and coordinates. Filter by stars and nightly price. Useful for travel price research and rate comparison. Runs the Apify Actor tacps126/google-hotels on your Apify account (about $0.002 per hotel; spend per call is capped at $0.5).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locations": "<locations>"
    },
    "name": "search_google_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoCountry code that sets the currency and region, e.g. "us".us
check_inNoCheck-in date, YYYY-MM-DD. Leave out for Google's default dates.
languageNoLanguage code for names and texts, e.g. "en".en
check_outNoCheck-out date, YYYY-MM-DD.
locationsYesCities or places, e.g. ["Lisbon", "Shibuya, Tokyo"].
max_itemsNoMaximum results to return (default 50, max 1000). Cost scales with this.
min_starsNoLowest hotel class to keep, e.g. 4.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
more_resultsNoPage through more hotels per place.
max_nightly_priceNoHighest nightly price to keep, in USD.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (which already declare readOnly, idempotent, open-world, non-destructive), the description discloses the commercial profile: it runs the tacps126/google-hotels Actor on the caller's own Apify account at roughly $0.002 per hotel with a $0.5 per-call spend cap. It also notes that omitting dates falls back to Google's default dates. That cost/account context is exactly the kind of behavior an agent needs to decide whether and how to call.

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?

It is front-loaded with the core purpose and then filters, use case, and cost, which is a sensible order. The long middle enumeration of return fields is somewhat wasteful given an output schema exists, and the cost note buried at the end is arguably the most decision-relevant detail.

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?

For a ten-parameter, open-world search with a nested escape-hatch object, the definition covers purpose, filterability, date fallback behavior, output contents, and per-call cost — and an output schema plus rich annotations carry the rest. Nothing an agent needs in order to call it correctly and predict the bill is missing.

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 description coverage is 100%, so all ten parameters including the nested extra_input are already documented. The description's only added parameter meaning is the stars/nightly-price filtering sentence, which mostly restates min_stars and max_nightly_price; it says nothing extra about country/currency interaction, more_results paging, or when extra_input is worth using. Baseline 3 applies.

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 definition opens with a concrete verb/resource pairing — hotels for a city or place from Google Hotels for given dates — and then enumerates exactly what comes back (name, hotel class, rating, review count, prices with/without taxes, deal vs usual price, check-in/out times, coordinates). Any of the sibling tools (news, jobs, grants, recalls) are clearly a different domain, so an agent can route here without inspecting the schema.

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 states the use case plainly ("travel price research and rate comparison") and notes the built-in narrowing options (stars and nightly price). It does not give explicit when-not conditions or name an alternative, but no sibling in the catalog overlaps with hotel price search, so the practical ambiguity is low.

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