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-14"}}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Destination or point of interest.
`rooms`	No	The number of rooms, Number of rooms must be lower than or equal to the number of adults
`adults`	No	The number of adults.
`arrival`	Yes	The arrival date in YYYY-MM-DD format, today is 2026-09-14. 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.
`country`	No	ISO alpha-2 country code that determines market-specific pricing and content. Default: US.	US
`filters`	No	The filters that you want to apply to the search. Set true or false for each filter. Multiple filters can be selected.
`children`	No	The number of children.
`currency`	No	ISO 4217 currency code used to display prices. Default: USD.	USD
`language`	No	Language code for translated content (e.g. EN_US, DE_DE, ZH_HANS_CN). Default: EN_US.	EN_US
`departure`	Yes	The departure date in YYYY-MM-DD format, today is 2026-09-14. 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_rating`	No	The hotel rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
`children_ages`	No	Dashed separated list of children ages, e.g. 10-12-14
`review_rating`	No	The guest review rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 14, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-13.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-14.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-13.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-14.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedSep 13, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-11.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-13.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-11.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-13.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-08.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-11.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-08.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-11.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedSep 9, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-06.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-08.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-06.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-08.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedSep 6, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-03.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-06.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-03.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-06.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedSep 3, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-01.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-03.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-01.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-03.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedSep 1, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-30.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-09-01.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-30.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-09-01.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 30, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-27.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-30.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-27.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-30.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 27, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-25.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-27.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-25.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-27.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-24.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-25.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-24.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-25.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 24, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-21.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-24.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-21.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-24.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 22, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-19.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-21.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-19.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-21.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 19, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-17.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-19.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-17.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-19.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 17, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-14.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-17.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-14.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-17.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 14, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-12.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-14.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-12.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-14.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 12, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-10.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-12.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-10.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-12.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 10, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-08.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-10.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-08.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-10.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 8, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-06.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-08.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-06.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-08.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 6, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-04.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-06.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-04.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-06.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 4, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-02.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-04.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-02.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-04.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedAug 2, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-31.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-08-02.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-31.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-08-02.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 31, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-28.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-31.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-28.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-31.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 28, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-26.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-28.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-26.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-28.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 26, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-24.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-26.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-24.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-26.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 24, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-21.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-24.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-21.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-24.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 21, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-19.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-21.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-19.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-21.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 19, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-17.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-19.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-17.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-19.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 17, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-15.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-17.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-15.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-17.\n\n\t\tThe 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.\n\t\t"

Changed3 schema fields changedJul 15, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-13.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-15.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-13.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-15.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / language / enum

Previous value: -[
-  "AR145",
-  "CS_CZ",
-  "DA_DK",
-  "DE_AT",
-  "DE_CH",
-  "DE_DE",
-  "EL_GR",
-  "EN_AU",
-  "EN_GB",
-  "EN_HK",
-  "EN_IE",
-  "EN_IL",
-  "EN_IN",
-  "EN_NZ",
-  "EN_PH",
-  "EN_SG",
-  "EN_US",
-  "EN_ZA",
-  "ES_AR",
-  "ES_CL",
-  "ES_CO",
-  "ES_ES",
-  "ES_MX",
-  "ES_PE",
-  "FI_FI",
-  "FR_BE",
-  "FR_CH",
-  "FR_FR",
-  "HE_IL",
-  "HU_HU",
-  "ID_ID",
-  "IT_IT",
-  "JA_JP",
-  "KO_KR",
-  "MS_MY",
-  "NL_BE",
-  "NL_NL",
-  "NO_NO",
-  "PL_PL",
-  "PT_BR",
-  "PT_PT",
-  "RO_RO",
-  "RU_RU",
-  "SV_SE",
-  "TH_TH",
-  "TR_TR",
-  "UK_UA",
-  "VI_VN",
-  "ZH_HANS_CN",
-  "ZH_HANT_HK",
-  "ZH_HANT_TW"
-]New value: +[
+  "AR145",
+  "CS_CZ",
+  "DA_DK",
+  "DE_AT",
+  "DE_CH",
+  "DE_DE",
+  "EL_GR",
+  "EN_AU",
+  "EN_GB",
+  "EN_HK",
+  "EN_IE",
+  "EN_IN",
+  "EN_NZ",
+  "EN_PH",
+  "EN_SG",
+  "EN_US",
+  "EN_ZA",
+  "ES_AR",
+  "ES_CL",
+  "ES_CO",
+  "ES_ES",
+  "ES_MX",
+  "ES_PE",
+  "FI_FI",
+  "FR_BE",
+  "FR_CH",
+  "FR_FR",
+  "HE_IL",
+  "HU_HU",
+  "ID_ID",
+  "IT_IT",
+  "JA_JP",
+  "KO_KR",
+  "MS_MY",
+  "NL_BE",
+  "NL_NL",
+  "NO_NO",
+  "PL_PL",
+  "PT_BR",
+  "PT_PT",
+  "RO_RO",
+  "RU_RU",
+  "SV_SE",
+  "TH_TH",
+  "TR_TR",
+  "VI_VN",
+  "ZH_HANS_CN",
+  "ZH_HANT_HK",
+  "ZH_HANT_TW"
+]

Changed2 schema fields changedJul 13, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-11.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-13.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-11.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-13.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 11, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-09.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-11.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-09.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-11.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 9, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-07.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-09.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-07.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-09.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 7, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-06.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-07.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-06.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-07.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 6, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-03.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-06.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-03.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-06.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJul 3, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-29.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-07-03.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-29.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-07-03.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJun 29, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-24.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-29.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-24.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-29.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJun 24, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-18.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-24.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-18.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-24.\n\n\t\tThe 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.\n\t\t"

Changed9 schema fields changedJun 18, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-13.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-18.\n\n\t\tThe 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.\n\t\t"

addedInput schema / properties / country

Added value: +{
+  "default": "US",
+  "description": "ISO alpha-2 country code that determines market-specific pricing and content. Default: US.",
+  "enum": [
+    "AE",
+    "AR",
+    "AT",
+    "AU",
+    "BE",
+    "BR",
+    "CA",
+    "CH",
+    "CL",
+    "CO",
+    "CZ",
+    "DE",
+    "DK",
+    "EG",
+    "ES",
+    "FI",
+    "FR",
+    "GB",
+    "GR",
+    "HK",
+    "HU",
+    "ID",
+    "IE",
+    "IL",
+    "IN",
+    "IT",
+    "JP",
+    "KR",
+    "MX",
+    "MY",
+    "NL",
+    "NO",
+    "NZ",
+    "PE",
+    "PH",
+    "PL",
+    "PT",
+    "RO",
+    "RU",
+    "SA",
+    "SE",
+    "SG",
+    "TH",
+    "TR",
+    "TW",
+    "UA",
+    "US",
+    "VN",
+    "ZA"
+  ],
+  "type": "string"
+}

addedInput schema / properties / currency

Added value: +{
+  "default": "USD",
+  "description": "ISO 4217 currency code used to display prices. Default: USD.",
+  "enum": [
+    "AED",
+    "ARS",
+    "AUD",
+    "BRL",
+    "CAD",
+    "CHF",
+    "CLP",
+    "CNY",
+    "COP",
+    "CZK",
+    "DKK",
+    "EGP",
+    "EUR",
+    "GBP",
+    "HKD",
+    "HUF",
+    "IDR",
+    "ILS",
+    "INR",
+    "JPY",
+    "KRW",
+    "MXN",
+    "MYR",
+    "NOK",
+    "NZD",
+    "PEN",
+    "PHP",
+    "PLN",
+    "RON",
+    "RUB",
+    "SAR",
+    "SEK",
+    "SGD",
+    "THB",
+    "TRY",
+    "TWD",
+    "UAH",
+    "USD",
+    "VND",
+    "ZAR"
+  ],
+  "type": "string"
+}

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-13.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-18.\n\n\t\tThe 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.\n\t\t"

removedInput schema / properties / id

Removed value: -{
-  "description": "\n\t\tThe ID of the location that you want to search for.\n\t\t",
-  "type": "number"
-}

addedInput schema / properties / language

Added value: +{
+  "default": "EN_US",
+  "description": "Language code for translated content (e.g. EN_US, DE_DE, ZH_HANS_CN). Default: EN_US.",
+  "enum": [
+    "AR145",
+    "CS_CZ",
+    "DA_DK",
+    "DE_AT",
+    "DE_CH",
+    "DE_DE",
+    "EL_GR",
+    "EN_AU",
+    "EN_GB",
+    "EN_HK",
+    "EN_IE",
+    "EN_IL",
+    "EN_IN",
+    "EN_NZ",
+    "EN_PH",
+    "EN_SG",
+    "EN_US",
+    "EN_ZA",
+    "ES_AR",
+    "ES_CL",
+    "ES_CO",
+    "ES_ES",
+    "ES_MX",
+    "ES_PE",
+    "FI_FI",
+    "FR_BE",
+    "FR_CH",
+    "FR_FR",
+    "HE_IL",
+    "HU_HU",
+    "ID_ID",
+    "IT_IT",
+    "JA_JP",
+    "KO_KR",
+    "MS_MY",
+    "NL_BE",
+    "NL_NL",
+    "NO_NO",
+    "PL_PL",
+    "PT_BR",
+    "PT_PT",
+    "RO_RO",
+    "RU_RU",
+    "SV_SE",
+    "TH_TH",
+    "TR_TR",
+    "UK_UA",
+    "VI_VN",
+    "ZH_HANS_CN",
+    "ZH_HANT_HK",
+    "ZH_HANT_TW"
+  ],
+  "type": "string"
+}

removedInput schema / properties / ns

Removed value: -{
-  "description": "\n\t\tThe NS of the location that you want to search for.\n\t\t",
-  "type": "number"
-}

addedInput schema / properties / query

Added value: +{
+  "description": "Destination or point of interest.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "ns",
-  "id",
-  "arrival",
-  "departure"
-]New value: +[
+  "query",
+  "arrival",
+  "departure"
+]

Changed2 schema fields changedJun 13, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-08.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-13.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-08.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-13.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJun 9, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-03.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-08.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-03.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-08.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedJun 3, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-05-26.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-06-03.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-05-26.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-06-03.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedMay 26, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-05-18.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-05-26.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-05-18.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-05-26.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedMay 18, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-05-12.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-05-18.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-05-12.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-05-18.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedMay 12, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-05-03.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-05-12.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-05-03.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-05-12.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedMay 4, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-04-27.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-05-03.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-04-27.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-05-03.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedApr 27, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-04-17.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-04-27.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-04-17.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-04-27.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedApr 18, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-04-11.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-04-17.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-04-11.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-04-17.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedApr 11, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-04-08.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-04-11.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-04-08.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-04-11.\n\n\t\tThe 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.\n\t\t"

Changed2 schema fields changedApr 8, 2026

changedInput schema / properties / arrival / description

Previous value: -"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-03-30.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe arrival date in YYYY-MM-DD format, today is 2026-04-08.\n\n\t\tThe 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.\n\t\t"

changedInput schema / properties / departure / description

Previous value: -"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-03-30.\n\n\t\tThe 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.\n\t\t"New value: +"\n\t\tThe departure date in YYYY-MM-DD format, today is 2026-04-08.\n\n\t\tThe 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.\n\t\t"

AddedMar 31, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits itself. It explains the live metasearch nature and what results contain, which gives some insight into side effects (read-only search operation). However, it does not mention pagination, result limits, network dependency, or other operational details that an agent might need to know. The description covers the basics but lacks deeper transparency.

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?

The main description is composed of four focused sentences, covering what it does, what it returns, what options it supports, and usage guidance. It is not overly verbose, but the appended 'Additional Information' JSON adds unnecessary noise, slightly detracting from the otherwise concise structure.

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

Completeness3/5

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

Given the tool's complexity (13 parameters, nested objects, no output schema), the description does a reasonable job of conveying purpose, result content, and filter capabilities. The substantial schema coverage compensates for missing details. However, with no output schema, vague statements like 'returns results with price...' leave return structure underspecified, and there is no discussion of result count or pagination behavior. Overall adequate but not complete.

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 baseline is 3. The description provides a high-level overview of supported parameters ('date range, guest/room configuration, and filters for star rating, guest rating, and amenities'), but it does not add syntax, defaults, or interactions beyond what the schema already states. It adds marginal value but remains consistent with 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?

The description clearly states the tool's primary action: 'Search live hotel and accommodation listings by destination or point of interest'. It also identifies the output ('price, rating, amenities, and a link per property') and scopes its use to 'destination- or place-name-based lodging search', which differentiates it from sibling tools like 'trivago_trivago-accommodation-radius-search' and 'trivago_trivago-destination-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?

The description gives an explicit guidance: 'Use for destination- or place-name-based lodging search.' This tells the agent when to choose this tool, but it does not name alternative tools or state when not to use it. The sibling names (e.g., 'trivago_trivago-accommodation-radius-search') imply the distinction, so the guidance is clear but not fully exhaustive.

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

All MolTravel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

trivago_trivago-accommodation-search

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources