Skip to main content
Glama

trivago hotel prices for a destination: the hotels trivago

travel_trivago
Read-only

trivago hotel prices for a destination: the hotels trivago lists for a city search (usually ~35) with name, location note, lowest price shown per night, guest rating out of 10 with review count, stars and trivago URL, plus trivago's destination price facts (typical nightly range, cheapest and most expensive month). Prices are in the currency trivago picks for the visitor region (reported in the output); not a dated availability search. Related tools on this server, for a different need: travel_agoda when you need top hotels in a city from Agoda's city guide page: about 10; travel_momondo when you need momondo flight prices from its public route page for two. 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": {
      "city": "<city>"
    },
    "name": "travel_trivago"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesDestination, e.g. Rome, Paris, New York

Output Schema

NameRequiredDescriptionDefault
countNo
factsNo
queryNo
hotelsNo
sourceNo
currencyNo
checkedAtNo
fromPriceNo
destinationNo
fromPriceTextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds real behavior: result volume (~35), currency selection driven by visitor region rather than a caller argument, and a cost model of $0.002 per successful call via x402 with no charge on failures. That pricing x402 detail is the kind of context an agent needs before spending, though it does not say whether results are cached or how listings are ordered.

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-loaded with the output shape and the availability caveat before alternatives and price, so an agent can bail out early if it wants a dated search. The phrasing is dense but the awkward repetition in "the hotels trivago lists" and the long parenthetical currency/payment clause cost it a point.

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 one-parameter listing tool, the definition covers what is returned, the scale of results, the currency caveat, what it is not, when to pick a sibling, and the billing model. With an output schema present it does not need to document return values in detail, and nothing an agent needs in order to call it correctly 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?

There is a single required parameter with 100% schema description coverage including examples (Rome, Paris, New York), so the schema already carries the semantics. The description only restates it as a city/destination search and adds nothing about format, disambiguation, or handling of ambiguous city names — baseline 3 is appropriate.

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 resource and verb: hotels trivago lists for a city search, with the expected result count (~35), the per-hotel fields returned, and destination-level price facts. It also names the siblings (travel_agoda, travel_momondo) it is not, so an agent can separate it from other hotel and flight tools without opening schemas.

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?

Gives an explicit negative boundary ("not a dated availability search") and names two alternatives with the exact condition that selects each (Agoda for top hotels from a city guide page, momondo for flight prices on a route for two). The when-to-use logic is fully stated rather than inferred.

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