CasaSAPO

View saved version →

---
name: casasapo-property-search
description: Search current property listings in Portugal through CasaSAPO. Use whenever a user naturally asks to buy, rent, or holiday-rent a house, apartment, room, land, or commercial property in Portugal, even if they do not mention CasaSAPO. Also use for details of a listing returned by CasaSAPO, to contact advertisers on returned listings, or to create property search alerts. Do not use for properties outside Portugal or when the user explicitly asks to search the web.
---

Use the CasaSAPO MCP tools as the source of truth for listings. Reply in the user's language while preserving returned property names, references, prices, and URLs exactly.

1. When the user asks what CasaSAPO can do through this MCP client, how it works, or how to start, call `get_mcp_guidance`. Do not call it when the user has a specific action request.
2. Identify the operation, location, property category, and constraints. If operation, location, or category is missing, ask only for the missing item; do not guess. Use `get_search_context` when current category IDs, condition IDs, or feature tokens are needed.
3. For every complete Portugal property-search request, call `search` in the same turn. Preserve the user's complete location wording in `locationQuery`; set `locationLevel` only when the user explicitly identifies the administrative level. If the response status is `location_ambiguous`, present only the returned `locationOptions`, ask the user to choose, and repeat the same search using exactly the selected option's `selectionToken` as `locationSelectionToken`, without `locationQuery` or `locationLevel`. Never invent or alter the token. If the status is `location_not_found`, ask the user to confirm or refine the location. If it is `location_selection_invalid`, ask for the location again.
4. Present only `searchTitle`, `count`, `searchUrl`, and listings/URLs returned by the server. When the client supports widgets, call `render_listings_widget` with the selected listings. Do not construct search URLs, add tracking parameters, infer a total, or invent results, prices, availability, identifiers, or property characteristics. Treat an empty result as no match and offer only a user-approved refinement.
5. Call `detail` only for a specific returned listing ID and system ID, or reference. Do not browse or infer details for a listing that the server did not return, and do not claim that the property or advertiser has been independently verified.
6. When a user asks about CasaSAPO, rental safety, private-property publication, account help, or support, call `get_casasapo_guidance` with the matching topic. For rental safety, never recommend a deposit, reservation fee, rent, or other payment before independent verification of the advertiser and property.
7. When the user explicitly asks to contact an advertiser for a returned listing (e.g. asking for more information or requesting a viewing), call `submit_lead` with the listing ID and optional message. This tool uses the authenticated CasaSAPO account (via OAuth 2.0) internally; never ask the user for personal contact details (name, email, or phone). The user's explicit request to contact is sufficient confirmation.
8. When the user asks to create an alert for new listings or price changes, call `create_alert` with the search criteria or listing ID. This tool uses the authenticated CasaSAPO account (via OAuth 2.0) internally; never ask the user for personal contact details. Confirm the criteria with the user before creation.
9. If a tool reports an error, state that clearly. If it returns an empty result, explain that no matching listing was found and offer to refine the search.

Referenced files: 1 — file references are metadata, not package contents.