add_package_to_cart
ChatGPTAdd a package offering to an existing cart (quantity is always 1). Requires a booking interval step. Do not use for products or services.
add_rental_product_to_cart
ChatGPTAdd a rental product to an existing cart (quantity is always 1). Use when the user wants to rent a product for a time period. Requires a booking interval step. Do not use for outright purchases, services, or packages.
add_sell_product_to_cart
ChatGPTAdd a for-sale (non-rental) product to an existing cart. Use when the user wants to purchase a product outright. Do not use for rentals, services, or packages.
create_app_deep_link
ChatGPTCreate an order bridge URL for an existing order. Returns a landing /deeplink link for the user plus app/OneLink fallbacks. Use after checkout when the user should open order details, chat, or rating in the app or browser. Share the url field with the user. Do not use for cart checkout; use create_order_link for that.
create_or_get_cart
ChatGPTCreate a cart session or fetch an existing cart by cartCode. Use before add_cart_item/update_cart_item/remove_cart_item. Do not use for catalog search, availability checks, or final order lookup.
create_order_link
ChatGPTCreate a checkout bridge URL for a prepared cart. Use after cart setup is complete and user is ready to proceed to payment/checkout. Do not use for order status retrieval; use get_order for that.
get_availability
ChatGPTCheck free and booked slots for a specific offering at a specific warehouse in a time range. Use after you already know the offering and warehouse IDs (for example after search_catalog / search_more_offerings). For rental products (productType="rent") you MUST also pass pricingOptionId from the search result — the backend rejects rental availability without it. Do not use for discovery/filtering across many items; use search_catalog / search_more_offerings for that.
get_offerings
ChatGPTCRITICAL: 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
ChatGPTCRITICAL: 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_order
ChatGPTFetch order details for an existing order. Use when the user asks for order status/details after checkout. Do not use for cart creation, checkout link generation, or catalog search.
remove_cart_item
ChatGPTRemove an existing line item from a cart. Use only when the user explicitly wants to delete an item from the cart. Do not use for quantity/date changes; use update_cart_item for edits.
search_catalog
ChatGPTCRITICAL: 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_more_offerings
ChatGPTCRITICAL: 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.
update_cart_item
ChatGPTUpdate 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.