Skip to main content
Glama

Google Travel hotels and vacation rentals for a place

travel_google_travel
Read-only

Google Travel hotels and vacation rentals for a place (about 20, Google's order): name, type, lowest price and currency (Google picks currency by server region), deal flag and % below usual, guest rating with review count and star distribution, hotel class, amenities, topics guests mention, eco-certified flag and link. Optional stay dates; otherwise Google's default dates (returned). Related tools on this server, for a different need: travel_google_hotels_price when you need lowest nightly hotel prices for a city and stay dates; travel_google_flights when you need One-way flight options with prices from Google Flights. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "place": "<place>"
    },
    "name": "travel_google_travel"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoProperties to return, 1 to 40 (default 20)
placeYesCity or area, e.g. Lisbon, Rome Trastevere
checkinNoCheck-in YYYY-MM-DD (optional, with checkout)
checkoutNoCheck-out YYYY-MM-DD (optional, with checkin)

Output Schema

NameRequiredDescriptionDefault
countNo
placeNo
totalNo
sourceNo
checkinNo
checkoutNo
checkedAtNo
propertiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds ordering, result count, currency selection by server region, default-date behavior, per-call cost, and failed-call non-charge. These are meaningful invocation details beyond annotations and do not contradict them.

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?

Front-loads the purpose and returned fields, then alternatives and cost. It is dense but nearly every clause conveys useful context; the long first sentence slightly reduces scanability.

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 complex open-world search tool with an output schema, it covers result fields, default dates, currency behavior, cost, and related alternatives. Little an agent needs in order to call it correctly is missing, and the output schema already handles return structure.

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; the description adds the consequence of omitting checkin/checkout, namely that Google default dates are used and returned. It reinforces the about-20 result default but adds little else beyond the schema for place or limit.

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 the specific resource and scope: Google Travel hotels and vacation rentals for a place. It lists the returned fields and names sibling tools for different needs, so an agent can distinguish it from travel_google_hotels_price without opening either 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?

Explicitly routes price-focused hotel queries to travel_google_hotels_price and flight queries to travel_google_flights, and explains that stay dates are optional with Google default dates. It does not state when to prefer other hotel sources or when not to use this tool, so it lacks full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources