Update to Listint

{
  "description": "Search UAE real-estate listings on Listint — apartments, villas, townhouses, buildings, land and developer projects — by area, budget, bedrooms, size, amenities or developer. Use when someone wants to find, browse, filter or price-check property to buy or rent in the UAE, or asks what is available in a specific community. Do not use for mortgages, legal or tax advice, or property valuation.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 417
    },
    {
      "relative_path": "assets/listint-icon.png",
      "size_in_bytes": 16253
    }
  ],
  "name": "property-search",
  "skill_md_contents": "---\nname: property-search\ndescription: Search UAE real-estate listings on Listint — apartments, villas, townhouses, buildings, land and developer projects — by area, budget, bedrooms, size, amenities or developer. Use when someone wants to find, browse, filter or price-check property to buy or rent in the UAE, or asks what is available in a specific community. Do not use for mortgages, legal or tax advice, or property valuation.\n---\n\n# Searching Listint\n\nListint indexes live UAE property listings. `search_listings` finds them;\n`get_listing_details` returns one record by id. Both are read-only.\n\n## Pick the right collection\n\n`collection` is the first decision and the tools behave differently per value.\n\n| Value | Holds | Use when |\n|---|---|---|\n| `unit` | Individual homes: apartments, villas, townhouses | Almost every buyer question. The **only** collection with bedroom, bathroom, property-type and amenity data |\n| `property` | Standalone assets: whole buildings, compounds, land, warehouses | \"building\", \"plot\", \"land\", \"compound\", commercial assets |\n| `project` | Developer developments | A named development, a launch, or a developer's portfolio |\n\nNever send `bedrooms`, `bathrooms`, `property_type` or `amenities` with\n`collection: \"project\"` — projects hold none of that data. The response will\nsay so in `unsupported_filters`, and the constraint the user asked for will not\nhave been applied.\n\n## Only filter on what was actually said\n\nSet a filter when the user stated it. Do not infer a budget, a bedroom count, a\nlocation or a property type from context, and do not carry filters over from an\nearlier search unless the user is clearly refining that same search. An\nunfiltered search that returns something is more useful than a guessed filter\nthat returns nothing.\n\n## Counts are lists, so ranges work\n\n`bedrooms` and `bathrooms` take arrays. Expand ranges rather than dropping them:\n\n- \"3 bedroom\" → `[3]`\n- \"2 or 3 beds\" → `[2, 3]`\n- \"at least 4 beds\" → `[4, 5, 6, 7, 8, 9]`\n- \"up to 2 beds\" → `[0, 1, 2]`\n- \"studio\" → `[0]`\n\n## Locations\n\n`locations` is an array, so \"Al Reem Island or Saadiyat\" is one search. Pass the\nplace names as the user said them, in **English** — Arabic place names do not\ncurrently match and will be dropped from the filter. `locations` is the area\nbeing searched, never the user's own position.\n\n## Sorting\n\nMap the user's wording: \"cheap\", \"cheapest\", \"affordable\", \"lowest price\" →\n`price_asc`. \"expensive\", \"most expensive\", \"luxury\", \"highest price\" →\n`price_desc`. Otherwise leave it alone.\n\n## Reading the response honestly\n\nTwo fields change what you must tell the user:\n\n- **`relaxed_filters`** — the exact search found nothing, so these constraints\n  were dropped to return something. Say plainly that these are not exact\n  matches and name what was relaxed, before listing anything.\n- **`unsupported_filters`** — this collection has no data for that filter, so it\n  was ignored. Say which constraint could not be applied and suggest searching\n  `unit` instead if that would help.\n- **`uncovered_location`** — Listint indexes nothing in the place that was\n  asked for. Say so plainly. Do not offer listings from anywhere else as\n  substitutes, and do not re-run the search with the location removed.\n\nOther things worth knowing when you summarise results:\n\n- Prices are **AED**; sizes are **sqft**.\n- A missing `price` means the price is not published — say \"price on request\"\n  rather than implying it is free or cheap.\n- `bedrooms: 0` on a unit means **studio**. A bedroom count also restricts the\n  search to homes, so a studio search will not return shops or warehouses.\n- `category` is `Sale` or `Rent`. A rent price is the **annual** rent, so say\n  \"per year\" rather than quoting it like a purchase price.\n- `completion_percentage` is construction progress, not a discount or a rating.\n- `agency` is who listed it; `developer` is who built it. They differ.\n- Every listing carries a `url`; link to it rather than describing where to look.\n\n## Coverage\n\nCoverage is concentrated in the **United Arab Emirates** — principally Abu Dhabi\nand Dubai, with some listings in Ras Al Khaimah — plus a smaller selection of\nbuildings and projects in Egypt, the United Kingdom, Oman, Morocco, Latvia and\nEthiopia. It is uneven and it changes: a community that has rentals may have\nnothing for sale, and vice versa.\n\nDo not pre-judge what exists from this paragraph — run the search and read what\ncomes back. When the search finds nothing in the requested place it returns\n`uncovered_location`; say that Listint has no listings there and stop, rather\nthan offering somewhere else as though it matched.\n\n`category` separates the two markets: `Sale` to buy, `Rent` to rent. Set it only\nwhen the user made the intent explicit, and never swap one for the other — a\nrental is not an answer to someone who wants to buy.\n\n## Following up on a result\n\n`get_listing_details` takes the `collection` and the `id` from a previous\nsearch result. Use it when the user asks about one specific listing rather than\nrunning the same search again.\n"
}