Get property details
get_property_detailsWHEN: use it after search_availability when the traveller wants to compare or see more detail about one specific category, or asks "tell me more about G4". WHAT IT RETURNS: description, max_guests, bedrooms (text + count), size_sqm, zone, generic location ("La Patacona, Alboraya — 30 m from the sea" / "Valencia city, close to the centre"), location_summary (how long to the old town, tram, airport…), highlights (terrace, sea views, pool, parking, m²), amenities (parking, pool_seasonal), up to 3 photos, trust (same block as search_availability), a booking_url_base to open the listing with no dates, and the Priority note. DO NOT ask here for the exact street address or access codes: they are only sent to the guest by email after a booking is confirmed. EXAMPLE: {"id":"G4","language":"en"}.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>"
},
"name": "get_property_details"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Property/type ID (G1..G6 or G4B). | |
| language | No | Response language. Defaults to en. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| name | Yes | ||
| zone | Yes | ||
| trust | Yes | ||
| photos | Yes | ||
| bedrooms | Yes | ||
| location | Yes | ||
| size_sqm | Yes | ||
| amenities | Yes | ||
| highlights | Yes | ||
| max_guests | Yes | ||
| description | Yes | ||
| priority_url | Yes | ||
| priority_note | Yes | ||
| bedrooms_count | Yes | ||
| booking_url_base | Yes | ||
| location_summary | Yes |