Skip to main content
Glama

trivago_trivago-accommodation-radius-search

[trivago] Search live hotel and accommodation listings near specific coordinates — a landmark, address, venue, or neighborhood — aggregated via trivago's metasearch of major booking sites. Returns the same, filterable results as trivago-accommodation-search. Use when the user anchors their search to a place rather than a named destination (e.g. "near the stadium," "within walking distance of X").

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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-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.
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
latitudeYesLatitude of the search target location (landmark, address, or neighborhood — not the user's location).
departureYes 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.
longitudeYesLongitude of the search target location (landmark, address, or neighborhood — not the user's location).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
  2. Changed2 schema fields changed
    • 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"
  3. Changed2 schema fields changed
    • 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"
  4. Changed2 schema fields changed
    • 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"
  5. Changed2 schema fields changed
    • 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"
  6. Changed2 schema fields changed
    • 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"
  7. Changed2 schema fields changed
    • 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"
  8. Changed2 schema fields changed
    • 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"
  9. Changed2 schema fields changed
    • 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"
  10. Changed2 schema fields changed
    • 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"
  11. Changed2 schema fields changed
    • 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"
  12. Changed2 schema fields changed
    • 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"
  13. Changed2 schema fields changed
    • 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"
  14. Changed2 schema fields changed
    • 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"
  15. Changed2 schema fields changed
    • 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"
  16. Changed2 schema fields changed
    • 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"
  17. Changed2 schema fields changed
    • 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"
  18. Changed2 schema fields changed
    • 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"
  19. Changed2 schema fields changed
    • 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"
  20. Changed2 schema fields changed
    • 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"
  21. Changed2 schema fields changed
    • 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"
  22. Changed2 schema fields changed
    • 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"
  23. Changed2 schema fields changed
    • 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"
  24. Changed2 schema fields changed
    • 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"
  25. Changed2 schema fields changed
    • 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"
  26. Changed2 schema fields changed
    • 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"
  27. Changed2 schema fields changed
    • 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"
  28. Changed2 schema fields changed
    • 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"
  29. Changed3 schema fields changed
    • 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"
      +]
  30. Changed2 schema fields changed
    • 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"
  31. Changed2 schema fields changed
    • 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"
  32. Changed2 schema fields changed
    • 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"
  33. Changed2 schema fields changed
    • 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"
  34. Changed2 schema fields changed
    • 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"
  35. Changed2 schema fields changed
    • 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"
  36. Changed2 schema fields changed
    • 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"
  37. Changed2 schema fields changed
    • 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"
  38. Changed9 schema fields changed
    • 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"
    • 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"
      +}
    • changedInput schema / properties / latitude / description
      Previous value: -"\n\t\tThe latitude of the search target location (e.g. a landmark or address), not the user's personal location.\n\t\t"New value: +"Latitude of the search target location (landmark, address, or neighborhood — not the user's location)."
    • changedInput schema / properties / longitude / description
      Previous value: -"\n\t\tThe longitude of the search target location (e.g. a landmark or address), not the user's personal location.\n\t\t"New value: +"Longitude of the search target location (landmark, address, or neighborhood — not the user's location)."
    • removedInput schema / properties / radius
      Removed value: -{
      -  "description": "\n\t\tThe radius in meters that you want to search for.\n\t\t",
      -  "type": "number"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "radius",
      -  "latitude",
      -  "longitude",
      -  "arrival",
      -  "departure"
      -]New value: +[
      +  "latitude",
      +  "longitude",
      +  "arrival",
      +  "departure"
      +]
  39. Changed2 schema fields changed
    • 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"
  40. Changed2 schema fields changed
    • 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"
  41. Changed2 schema fields changed
    • 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"
  42. Changed2 schema fields changed
    • 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"
  43. Changed2 schema fields changed
    • 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"
  44. Changed2 schema fields changed
    • 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"
  45. Changed2 schema fields changed
    • 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"
  46. Changed2 schema fields changed
    • 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"
  47. Changed2 schema fields changed
    • 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"
  48. Changed2 schema fields changed
    • 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"
  49. Changed2 schema fields changed
    • 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"
  50. Added

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool is a read-only search (live listings, metasearch aggregation) and notes that results are equivalent to trivago-accommodation-search. However, it does not disclose behaviors like missing radius parameter, result limits, pagination, or error handling. It is not misleading but lacks depth beyond the basic operation.

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?

The description is two sentences, front-loads the core action and scope, and includes the use-case distinction and alternative in minimal words. There is no fluff or redundancy; every sentence earns its place.

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?

With 14 parameters, nested objects, and no output schema, the description is moderately complete. It clarifies the core scenario and mentions that results are same as the sibling, but it omits critical context like the absence of a radius parameter (despite the tool name), how the radius is derived, and what the output structure looks like. The schema covers parameters well, but the description does not fill in operational gaps sufficient for a complex tool.

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 14 parameters already have detailed descriptions. The tool description adds minimal parameter-level meaning—only reaffirming that coordinates refer to the target location and not the user's location, which is already in the schema. With full schema coverage, a baseline of 3 is appropriate, and the description does not compensate with extra context.

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 states a specific verb and resource: 'Search live hotel and accommodation listings near specific coordinates.' It clearly defines the target (landmark, address, venue, neighborhood) and explicitly distinguishes it from the sibling trivago-accommodation-search by noting it returns the same results but anchored to a place. This fully differentiates the tool's purpose.

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?

The description gives explicit when-to-use guidance: 'Use when the user anchors their search to a place rather than a named destination (e.g. "near the stadium," "within walking distance of X").' It contrasts with the named-destination scenario, implicitly directing agents to the sibling tool for such cases. The alternative is named directly, leaving no ambiguity.

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.