Skip to main content
Glama

chucho — Book Direct

Find vacation homes

search_properties

Search currently published properties. Use geographicArea for continents/subregions returned by get_filters(kind:geography), countries for an explicit ISO country union, and country/region/city for specific destinations. Filters combine with AND; unknown or hidden facts never satisfy a filter. Use organization with a returned organization.slug for its entire portfolio, or relatedTo with a published property ID for other homes from that organization, same locality first. Optional quoteMode:exact with arrival, departure and guests adds host availability/prices; quoteMode:estimate with explicit flexible bounds, nights and guests adds a labeled sample stay found across up to four near-term/future-month windows (explicit window, nights and guests required). Quote enrichment waits at most 2.5 seconds, may be pending/not_checked/limited, and does not filter or rank homes by availability. Use get_stay_estimate with stayQuote.estimate to finish a flexible sample, or get_stay_quote with stayQuote.request for exact dates. Unknown is not available; a sample is not availability for the traveler's actual dates. Inspect actual currency, completeness, checkedAt and expiresAt. Quotes reserve nothing. Omit quoteMode for pure catalog discovery.Price requests require a supplied party size and stay context. Exact dates use arrival/departure/guests. Flexible travel uses quoteMode:estimate with explicit estimateWindowStart/estimateWindowEnd, estimateNights and guests; resolve a supplied month into bounds and ask only for missing details before requesting or displaying any price. A brief clarification may come before catalog search; budget is optional in the same question. With sufficient inputs, complete bounded shortlisted checks without asking permission. Without these inputs, discover homes without quoteMode and show no prices in cards or prose. Never invent dates, stay length or party size. When price is requested, first inspect already-ready quotes and use displayedPropertyIds to identify the inline cards when supplied. Join pending checks for promising displayed homes before starting not_checked homes or off-screen alternatives, using the returned request or estimate. Make at most three follow-up checks in total; never check every card. A pending search quote can finish independently in the cards, so resolve selected pending checks before giving a budget conclusion. Compare confirmed available, complete stay totals in the requested currency against the budget; do not reject a supported match. When a supported budget match is found, recommend it with any material qualification; omit failed or unchecked alternatives unless a comparison is requested. If no match is confirmed and selected checks remain unresolved, say that briefly rather than claiming no home fits the budget or is available. Make status claims per returned quote evidence; never blanket-label other cards unchecked or unavailable, since they update separately. Inspect terminal ready failures and sample diagnostics internally; briefly state only material unknown price or availability, and stop unchanged retries. Catalog totals count matching published homes, never confirmed available or affordable homes. Sample diagnostic reasons describe attempted stays only, never the whole window. Returns compact comparison summaries with IDs, public facts and citations; use get_property for complete facts and photos. Follow nextPage with the same filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch public property names, locations and approved introduction text.
cityNo
pageNo
poolNo
placeNoPlace key from the live filter catalog.
boundsNoMap viewport as south,west,north,east in degrees; keeps homes whose public area center is inside it. West greater than east crosses the antimeridian.
guestsNoRental minimum sleeping capacity; for boutique hotels, actual adults for a one-room quote, with occupancy unconfirmed until that quote succeeds.
localeNoen
regionNo
arrivalNo
countryNo
featureNoCollection key from the filter catalog.
currencyNo
semanticNoRank indexed, eligible homes by text and photo similarity. Does not establish hard facts; no lexical fallback when unavailable.
amenitiesNoComma-separated amenity keys; every requested amenity must be explicitly present.
countriesNoExplicit union of ISO 3166-1 alpha-2 country/territory codes, e.g. [CR, PA]. A home must match one selected country; combines with geographicArea, country and every other filter using AND. Use available codes from get_filters; never silently substitute a narrower country for an area.
departureNo
quoteModeNoOptional price/availability enrichment. exact uses supplied dates and guests; estimate requires estimateWindowStart, estimateWindowEnd, estimateNights and guests for a clearly labeled sample within supplied flexible bounds. Search does not wait for every host or filter unknown homes out.
relatedToNoPublished property ID. Find other homes from its organization, same locality first, then region/country and other locations. Excludes the source property. Additional filters still combine with AND.
minBedroomsNo
minBathroomsNo
organizationNoExact organization slug returned on a property or in get_filters. Restricts results to that organization, across destinations.
estimateNightsNoSample-stay nights, required. Only with quoteMode:estimate.
geographicAreaNoExact geographic area key from get_filters(kind:geography), including continents and subregions. Americas includes North/Central/South America and the Caribbean. north-america includes Northern America, Central America and Caribbean; northern-america is the narrower UN M49 subregion. Filters by public ISO country/territory code; unknown locations never match. Combines with all other filters using AND.
accommodationTypeNoFilter by reviewed accommodation type. Hotel results represent one establishment; guest count requires a quote for one suitable room, never total hotel capacity.
estimateWindowEndNoLatest sample departure (YYYY-MM-DD), paired with estimateWindowStart. Window must fit estimateNights (required), at most 150 days.
estimateWindowStartNoEarliest sample arrival (YYYY-MM-DD), paired with estimateWindowEnd. Only with quoteMode:estimate. Preserve the traveler's flexible month or date range.
reassessPropertyIdsNoUp to four previously discussed public property IDs to reassess against this semantic request alongside fresh matches. Use when refining or comparing earlier suggestions. This reserves comparison slots only: current factual filters, indexed source ownership and every essential requirement still apply. It does not keep an old recommendation or establish fit. Omit for a new search without earlier candidates to reassess.
semanticPreferencesNoIndividual experiential preferences, each copied verbatim from semantic. Interpret the traveler in context: separate requested preferences without adding needs. Keep related words together when they describe one room, view or relationship. These are questions to assess, not property facts; omit for factual-only searches.
semanticRequirementsNoEssential trip requirements, each copied verbatim from semantic with all relationship and provenance qualifiers. Every one must have source-backed support before a home is returned. Preserve these from the conversation; ordinary preferences belong in semanticPreferences. Omit when no essential experiential requirements were stated. Interpret semanticRequirements as conditions the accommodation or its setting must satisfy. Preserve essential support for the traveler's primary activity and access needs, including when expressed indirectly. Preserve the traveler's complete context in semantic. When the traveler states an explicit offering condition together with their own plans, circumstances or reasons, copy the complete offering condition as the essential; do not create an additional standalone proof obligation for the traveler's plan or circumstance. Keep any context necessary to understand the condition, its scope and relationships. Do not broaden a specific access requirement into proof of every aspect of the trip, and do not drop an actual offering condition because it is motivated by a traveler's circumstances. When a circumstance leaves the required accommodation or access condition ambiguous, ask one short clarifying question before searching; do not submit the circumstance itself as a property-proof requirement. If the offering condition itself is ambiguous, clarify it in the real conversation instead of inventing a stricter condition.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
totalYes
localeYes
nextPageYes
pageSizeYes
semanticNo
relatedToYes
missingIdsNo
propertiesYes
organizationYes
displayedPropertyIdsNoProperty IDs in the initial inline photo cards, in display order; the explorer can display more homes. Only supplied for ChatGPT search_properties; prioritize their pending quote follow-ups.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.