Ivon

CRITICAL: right after this tool returns, paste structuredContent.reply verbatim as your first user-visible message — no intro, no summary, no paraphrase before it. Show the visual carousel only once per conversation: use search_catalog for the FIRST catalog search; for every later or refined search use search_more_offerings, which returns the same linked listings as text without re-rendering the carousel. Every listing must be a markdown link [name](url). Never plain text like "Beach Paddle Ball — $12" without the url. Use exact urls from structuredContent.items[]. Do not rewrite item names or drop links. Trip planning: if the user says "plan my trip" (or similar) without where + when + people, do NOT call this tool — ask for city/area, dates, and headcount first. When where, dates, and people are provided, structure the reply by trip dates and rentals in that location (tool builds the layout). Catalog only — not a hotel booking engine. "Places to stay" means bookable Ivon rentals/experiences in the destination city, not third-party hotels. The reply already ends with an add-to-cart follow-up — do not invent your own closing question. If the user then picks items to add, use structuredContent.items[].offeringId as the offeringId for the add_*_to_cart tools (chain create_or_get_cart → get_availability → add_*_to_cart). Pick the add tool by kind + productType: product+rent → add_rental_product_to_cart, product+sale → add_sell_product_to_cart, service → add_service_to_cart, package → add_package_to_cart. Search Ivon for bookable products, services, and packages (rentals/experiences). Vague trip requests ("plan my trip", "help plan vacation"): ask Where (city/area), When (dates), How many people — then call with city, fromDate, toDate, people. With full trip details, reply is grouped by date near the destination. If there is no exact match, the tool automatically returns the closest analogues (already labeled "closest alternatives" in the reply) — still paste structuredContent.reply verbatim; do not re-search or apologize separately. Examples: "plan my trip" → ask 3 questions first; "Clearwater Jul 5-7 4 people" → search and paste structuredContent.reply. Renders the visual results carousel — use this for the FIRST catalog search of a conversation only. Do NOT call this tool again after the first search: any later or refined search must use search_more_offerings, which returns the same listings without stacking another carousel. Legacy alias for 'search_catalog'.

get_offerings_with_ui

CRITICAL: right after this tool returns, paste structuredContent.reply verbatim as your first user-visible message — no intro, no summary, no paraphrase before it. Show the visual carousel only once per conversation: use search_catalog for the FIRST catalog search; for every later or refined search use search_more_offerings, which returns the same linked listings as text without re-rendering the carousel. Every listing must be a markdown link [name](url). Never plain text like "Beach Paddle Ball — $12" without the url. Use exact urls from structuredContent.items[]. Do not rewrite item names or drop links. Trip planning: if the user says "plan my trip" (or similar) without where + when + people, do NOT call this tool — ask for city/area, dates, and headcount first. When where, dates, and people are provided, structure the reply by trip dates and rentals in that location (tool builds the layout). Catalog only — not a hotel booking engine. "Places to stay" means bookable Ivon rentals/experiences in the destination city, not third-party hotels. The reply already ends with an add-to-cart follow-up — do not invent your own closing question. If the user then picks items to add, use structuredContent.items[].offeringId as the offeringId for the add_*_to_cart tools (chain create_or_get_cart → get_availability → add_*_to_cart). Pick the add tool by kind + productType: product+rent → add_rental_product_to_cart, product+sale → add_sell_product_to_cart, service → add_service_to_cart, package → add_package_to_cart. Search Ivon for bookable products, services, and packages (rentals/experiences). Vague trip requests ("plan my trip", "help plan vacation"): ask Where (city/area), When (dates), How many people — then call with city, fromDate, toDate, people. With full trip details, reply is grouped by date near the destination. If there is no exact match, the tool automatically returns the closest analogues (already labeled "closest alternatives" in the reply) — still paste structuredContent.reply verbatim; do not re-search or apologize separately. Examples: "plan my trip" → ask 3 questions first; "Clearwater Jul 5-7 4 people" → search and paste structuredContent.reply. Renders the visual results carousel — use this for the FIRST catalog search of a conversation only. Do NOT call this tool again after the first search: any later or refined search must use search_more_offerings, which returns the same listings without stacking another carousel.

search_catalog

CRITICAL: right after this tool returns, paste structuredContent.reply verbatim as your first user-visible message — no intro, no summary, no paraphrase before it. Show the visual carousel only once per conversation: use search_catalog for the FIRST catalog search; for every later or refined search use search_more_offerings, which returns the same linked listings as text without re-rendering the carousel. Every listing must be a markdown link [name](url). Never plain text like "Beach Paddle Ball — $12" without the url. Use exact urls from structuredContent.items[]. Do not rewrite item names or drop links. Trip planning: if the user says "plan my trip" (or similar) without where + when + people, do NOT call this tool — ask for city/area, dates, and headcount first. When where, dates, and people are provided, structure the reply by trip dates and rentals in that location (tool builds the layout). Catalog only — not a hotel booking engine. "Places to stay" means bookable Ivon rentals/experiences in the destination city, not third-party hotels. The reply already ends with an add-to-cart follow-up — do not invent your own closing question. If the user then picks items to add, use structuredContent.items[].offeringId as the offeringId for the add_*_to_cart tools (chain create_or_get_cart → get_availability → add_*_to_cart). Pick the add tool by kind + productType: product+rent → add_rental_product_to_cart, product+sale → add_sell_product_to_cart, service → add_service_to_cart, package → add_package_to_cart. Search Ivon for bookable products, services, and packages (rentals/experiences). Vague trip requests ("plan my trip", "help plan vacation"): ask Where (city/area), When (dates), How many people — then call with city, fromDate, toDate, people. With full trip details, reply is grouped by date near the destination. If there is no exact match, the tool automatically returns the closest analogues (already labeled "closest alternatives" in the reply) — still paste structuredContent.reply verbatim; do not re-search or apologize separately. Examples: "plan my trip" → ask 3 questions first; "Clearwater Jul 5-7 4 people" → search and paste structuredContent.reply. Returns the same linked listings as text WITHOUT re-rendering the carousel — use this for every follow-up or refined search after the first search_catalog call has already shown the carousel.

search_more_offerings

Update fields for an existing cart line item. Use when the user changes quantity, schedule, warehouse, delivery, or participant details. Do not use to add a new line item or remove one.

update_cart_item