Retrieves enriched information for a specific Viator experience, including detailed descriptions, highlights, imagery, pricing, and the click-out URL.The model should call this tool only when the user clearly refers to a specific experience—either by selecting it in the UI or by asking follow-up questions such as “Tell me more about…”;if multiple experiences were shown, the model must resolve ambiguity by asking which one the user means. This tool is intended for deepening experience understanding rather than search, and should only be invoked with a code previously returned by search_experiences.

Retrieves a curated list of Viator experiences based on required trip context (location and travel dates) and optional refiners (categories, kid-friendliness, budget, duration, time of day, etc.). The tool supports both low-intent queries (e.g., “things to do in London this weekend”) and high-intent queries (e.g., “kid-friendly cooking classes in July in Rome”). The model must ensure that location refers to a destination, not an attraction. E.g., “Paris, France” rather than “Eiffel Tower.” Locations should be passed, in English, in a consistent, human-readable geographic format such as "City, Country" or "Region, Country" or "Country", depending on the granularity provided by the user. The model must provide location (and, when possible, dates) before calling this tool, and may include additional refiners only when appropriately derived from user intent. The model may re-issue a refined searchExperiences call whenever the user adds, removes, or adjusts refinement criteria (e.g., kid-friendly, price range, shorter duration) to narrow or improve the results. If the tool returns zero results, the model must proactively guide the user toward a successful refinement. It should review the parameters used in the failed request and recommend the most appropriate based on the proposed logic:" If > 1 categories applied, suggest removing some categories. Eg: “It looks like those categories combined are too restrictive. Would you like to narrow it down?” If the query requests a specific feature (eg private tour), suggest removing this constraint. Eg: “Private tours may be limited in this area, would you like to consider group options too?” If duration (avg from/to) > XX, suggest trying a shorter duration. If duration (avg from/to) < XX, suggest trying a longer duration. If price constraint was applied, suggest widening (or removing) price limits. Else, suggest broaden location search. Eg: “Nothing matches in central Siena, should we try Tuscany or nearby towns?”