Search-cottages
search-cottagesFull Description
Search for holiday cottages in the UK.
IMPORTANT
- RE-CALL THIS TOOL when the user:
- Asks for different/closer/farther locations → use a more specific destination (e.g., "Liverpool" instead of "North West England")
- Wants to change dates, guests, price range, or amenities
- Asks for "more options", "cheaper", "better rated" → adjust sort or filters
- Asks for "top N" results → use the limit parameter
The destination parameter accepts both broad regions (Cornwall, Lake District) and specific towns/cities (Liverpool, Bath, York). For "closer to X" requests, use the specific city/town name as destination. Leave destination empty to search all of the UK.
Only works for UK destinations and for more than 2 nights.
Parameters (0 required, 14 optional)
adultsintegerNumber of adults (max 30 for large group bookings)
2childrenintegerNumber of children
0destinationstringUK location name. Leave empty to search all UK.
discountOnlybooleanOnly show discounted properties
FalseendDatestringEnd date to calculate duration
featuresarrayFeature filters: hottub, wifi, pool, sauna, parking, garden, barbecue, beach, golf, dishwasher, washingmachine, cot, highchair, fishing, coastal, fireplace
maxPricenumberMaximum price in GBP
minPricenumberMinimum price in GBP
nightsintegerDuration 2-28 nights
7pageinteger1petsintegerNumber of pets (filters to pet-friendly)
0sortstringrecommendedpriceAscpriceDescreviewDescrecommendedstartDatestringStart date in dd-MM-yyyy format
user_intentstringA concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and context to improve the overall user experience. - For short, self-contained prompts (e.g. "I want new shoes"), copy the user message as-is. - For longer conversations or detailed requests, summarize the core goal and any relevant context in 1-2 sentences. Focus on intent, constraints, and preferences - not the full dialogue. Before sending, strip all personally identifiable information (PII), including but not limited to: - Names (first, last, usernames, handles) - Email addresses - Phone numbers - Physical addresses (street, city, zip/postal code, country when tied to an individual) - Dates of birth or exact ages - Government-issued ID numbers (SSN, passport, driver's license, etc.) - Payment or financial information (card numbers, bank accounts, etc.) - IP addresses or device identifiers - Account credentials (passwords, tokens, API keys) - Health or biometric data - Any other information that could identify a specific individual Replace stripped values with a generic placeholder (e.g. "[name]", "[email]", "[address]"). Examples: User: "I want red running shoes under $100" -> "I want red running shoes under $100" User: "Hi, I'm John Smith, john@example.com, and I'm looking for flights from Paris to Tokyo for 2 adults departing around mid-June, budget around EUR2000 total" -> "Looking for flights from Paris to Tokyo for 2 adults, mid-June, budget ~EUR2000" User: "I need help resetting my password for account ID acct_12345" -> "I need help resetting my password for account ID [account_id]"