Skip to main content
Glama

MolTravel

by com.moltravel

trivago_trivago-accommodation-search

[trivago] Search live hotel and accommodation listings by destination or point of interest, aggregated via trivago's metasearch of major booking sites. Returns results with price, rating, amenities, and a link per property. Supports date range, guest/room configuration, and filters for star rating, guest rating, and amenities. Use for destination- or place-name-based lodging search.

Additional Information: {"knownInformation":{"currentYear":"2026","today":"2026-09-01"}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesDestination or point of interest.
roomsNo The number of rooms, Number of rooms must be lower than or equal to the number of adults
adultsNo The number of adults.
arrivalYes The arrival date in YYYY-MM-DD format, today is 2026-09-01. The arrival date MUST be before the departure date. If the arrival date is not in the future, notify the user that the arrival date is not in the future.
countryNoISO alpha-2 country code that determines market-specific pricing and content. Default: US.US
filtersNo The filters that you want to apply to the search. Set true or false for each filter. Multiple filters can be selected.
childrenNo The number of children.
currencyNoISO 4217 currency code used to display prices. Default: USD.USD
languageNoLanguage code for translated content (e.g. EN_US, DE_DE, ZH_HANS_CN). Default: EN_US.EN_US
departureYes The departure date in YYYY-MM-DD format, today is 2026-09-01. The departure date MUST be after the arrival date. If the departure date is not after the arrival date, notify the user that the departure date is not after the arrival date.
hotel_ratingNo The hotel rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
children_agesNo Dashed separated list of children ages, e.g. 10-12-14
review_ratingNo The guest review rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden. It explains the live metasearch aggregation, the return fields (price, rating, amenities, link), and supported search dimensions. It does not mention result limits or pagination, but for a search tool the core behavior is transparent enough.

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?

Three compact sentences with no filler: the action and return value are front-loaded, followed by supported options and the exact use-case. Every sentence earns its place, and the Additional Information is separate context rather than description bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 13 parameters, nested filter objects, and no output schema, the description is sufficient for selection and invocation: it names the expected return and the search criteria. It does not explain how country/currency/language affect results or mention result caps, but the schema covers the former and the core invocation is clear.

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 the schema already documents all 13 parameters thoroughly. The description only recaps categories like date range, guest/room configuration, and filters without adding new semantics, matching the baseline of 3.

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 live hotel and accommodation listings by destination or point of interest', aggregated via trivago's metasearch. Also describes return contents and filter capabilities, which clearly distinguishes it from sibling tools like trivago radius-search and price-trends.

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?

Provides clear intended use: 'Use for destination- or place-name-based lodging search.' This strongly implies coordinate/radius searches belong to a different tool, but it does not explicitly name the sibling trivago-accommodation-radius-search or state when not to use this tool.

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

All MolTravel toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation3/5

Most tools are namespaced by vendor and resource, so ferry, tour, flight, hotel, and experience searches are broadly distinguishable. However, hotel search exists in both skiplagged and trivago, ferryhopper_search_trips is a deprecated duplicate of search_trips_v2, and several skiplagged calendar/anywhere tools overlap in flight-price discovery, which can cause misselection.

Naming Consistency2/5

Naming conventions are mixed across the set: plain underscores (airports_search), vendor-prefixed underscores (ferryhopper_get_ports), redundant prefixes (skiplagged_sk_hotels_search, trivago_trivago-accommodation-search), and hyphenated sub-APIs (tourradar_b2b-tour-details, tourradar_vertex-tour-search). There is no consistent verb_noun pattern and at least one version-suffixed deprecated name.

Tool Count1/5

With 56 tools, the server falls into the extreme-mismatch count band. The breadth is partly explained by eight vendor integrations, but many lookups, near-duplicate searches, and deprecated tools could be consolidated or split into focused MCP servers.

Completeness4/5

The tool surface covers most of the travel-planning lifecycle: airports, airlines, visa rules, FCDO advice, flights, hotels, cars, ferries, experiences, and tours including search, details, and tour booking. The main gaps are that only tours have an actual booking flow and there is no update/cancel or post-booking management.

Resources