Novasol

Search for individual holiday properties across 18 European countries with Novasol. It returns individual bookable properties, not aggregate statistics (averages, counts, price trends) or historical data. Results order: results are returned most relevant first for the chosen sort, and the carousel renders them in that order. Each property's "position" field (1-based) is its slot in the carousel. Present or compare properties following this same order. Re-call this tool when the user: - Asks for different, closer, or farther locations - Wants to change dates, guests, price range, or amenities - Asks for cheaper or better-rated results (adjust sort or filters) Each search returns at most the top 48 properties and there is no next page. When the user asks for more results, do not repeat the same search: ask one or two refinement questions relevant to what they are looking for (a more specific area, dates, budget, amenities), then search again with the refined filters. Destination (required): pass a single location name (a town, region, or country), not a combination like "Dubrovnik, Croatia". Use the most specific name first (e.g. "Dubrovnik" rather than "Croatia"). Use the common English name for the place when one exists (e.g. "Tuscany" rather than the French "Toscane"); otherwise use the local name as written in the destination's own country. Avoid translating a place into a third language. If the location is not found, follow the retry guidance in the error response, retrying at most once. A destination is needed, since a Europe-wide search isn't available. When the user has not named a location, the next step is to find out which country or region they have in mind before searching rather than searching with an empty destination. Works for stays of 1 or more nights. Amenity / vibe requests: when the user describes a vibe or an amenity that isn't a concrete filter (e.g. "silliest extras", "most unusual", "romantic", "great for kids"), map it to the closest supported feature filter(s) where possible (see the features parameter — hot tub, pool, sauna, etc.). If it can't be mapped, still confirm a location, search it normally, and pick the standouts from the returned data; amenities, descriptions, or "extras" that aren't present in the results are best left out. Broad regions: when the user names a broad multi-country area ("Southern Europe", "the Mediterranean", "the south of Europe", "Scandinavia", "Central Europe"), passing it as the destination returns poor, mixed results. A single most-fitting supported country works better (e.g. Southern Europe / the Mediterranean → Italy, Spain or Croatia; Scandinavia → Denmark, Sweden or Norway): search that one country, then tell the user which country you defaulted to and that they can choose another. Coverage: Novasol covers continental Europe only. It does not offer properties in the UK (England, Scotland, Wales, Northern Ireland, the Channel Islands, the Isle of Man), nor in countries such as the Czech Republic, Ireland or Switzerland. A UK or otherwise unsupported destination has no results; if the user asks for one, letting them know Novasol does not cover it and offering the nearest supported alternative is the way to go. Dates: pricing and availability are only accurate when a startDate is set, so it's better to set one whenever the user has hinted at timing. - No timeframe at all (user said nothing about when): leave startDate empty and search date-agnostic. - A timeframe but no exact day (a month like "August", a season, "this summer", "next month"): resolve it to a concrete Saturday start with a 7-night stay. If the named month is the current month, use the next upcoming Saturday; otherwise use the first Saturday of that month (roll to next year if the month has already passed this year). Compute the date relative to today and pass it as startDate in dd-MM-yyyy format. - An exact date or explicit duration: use exactly what the user said. - Default nights to 7 (Saturday to Saturday) whenever the user does not specify a length. - Whenever a default date or default duration was applied, telling the user which dates you assumed (e.g. "I've shown a 7-night stay from Sat 1 Aug — let me know if you had other dates in mind") and inviting them to adjust works well. This can count as your one refinement suggestion. After the carousel renders: - Recommend 2-3 standouts, in carousel-position order (position 1 first). A property at a position the user has not scrolled to is best not described as already on screen. - Draw on the returned fields: name, location, region, price, wasPrice (pre-discount price), reviewScore, sleeps, bedrooms, petsAllowed. Photos, full amenity lists, exact map location, and booking live on the property card, so point the user there for anything else. - If the user asks about an amenity that isn't in the data (hot tub, wifi, pool…), re-search with that feature filter or point to the card rather than guessing. - If filters were relaxed or the destination was broadened, say so transparently. - End with one refinement suggestion the user has not already addressed (dates, budget, features, area) rather than a list of everything they could change.

search-properties