James Villas

Search for handpicked holiday villas with James Villas across 8 Mediterranean European countries: Croatia, Spain (including the Balearic and Canary Islands), France, Italy, Greece, Montenegro, Cyprus, and Portugal. It returns individual bookable villas, 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 "more options", "cheaper", or "better rated" Destination: pass a single location name (a town, region, or country), not a combination like "Rovinj, Croatia". Use the most specific name first (e.g. "Istria" rather than "Croatia"). Use the common English name for the place when one exists (e.g. "Tuscany" rather than "Toscana"). Minor spelling variations are tolerated. If the location is not found, follow the retry guidance in the error response, retrying at most once. Leave it empty to search across all James Villas destinations. Coverage: James Villas covers Croatia, Spain (including the Balearic and Canary Islands), France, Italy, Greece, Montenegro, Cyprus, and Portugal only. A country's islands count as covered. It does not offer villas in the UK or elsewhere. Croatia has by far the deepest inventory; Montenegro, Cyprus, and Portugal have very few villas, so a search there coming back empty or thin is normal — offering a nearby supported country works well. Luxury requests: James Villas is a premium villa brand. When the user asks for luxury, spa, or wellness-style stays, map to the closest supported feature filter(s) — pool, hottub, sauna, wellness, steamroom, seaview, beachfront (see the features parameter). There is no gym filter; gyms and other unlisted amenities are best not promised — search normally and pick standouts from the returned data instead. 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. The search will assume a 7-night stay starting on a Saturday about 6 months ahead (the assumed date comes back in appliedFilters.startDate with startDateAssumed: true). When that happens, tell the user which dates were assumed and that they were picked arbitrarily, and invite them to share their actual travel dates. - 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. Stays are 2 to 28 nights. - 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 (total for the whole stay, never a nightly rate), wasPrice (pre-discount total), 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