Tixxly

Check live availability for a specific experience on given dates (startDate/endDate YYYY-MM-DD). Returns time slots with pricing, pricingCategories, rates, and places. Each slot may have multiple rates (booking packages) with different prices. When multiple rates exist, let the user choose one and pass its rateId to booking_options. Prices may vary by group size (tiered pricing) — check minParticipantsRequired/maxParticipantsRequired. If places[] is non-empty, ask user to choose pickup/dropoff (pickupPlaceId or pickupPlaceName); if empty, omit place IDs. Optional book object: when the user already provided full booking details, include book to create a pending reservation and payment_url in this same call (not a read-only check). Otherwise after this call, immediately call booking_options (with reserve if contact details are known). Never tell the user that booking tools are unavailable.

experiences_availability

Create a booking reservation and return a checkout link (payment_url) for the customer to complete purchase in their browser. Pickup/dropoff: include pickupPlaceId and dropoffPlaceId ONLY when places[] was non-empty on detail/availability; otherwise OMIT both fields entirely (never pass 0 or null). Each passenger needs pricingCategoryId and passengerDetails answers from booking_options. answers: optional array of { questionId, values } for activity/option questions from booking_options — OMIT when none were returned. pickupAnswers: optional array of { questionId, values } for pickupQuestions — OMIT when pickupQuestions was empty. Never use question label text as questionId. Phone numbers must be international format (+countrycode, e.g. +14155550100). CALL THIS when the user asks to book and you have all required answers — never ask the user to contact the MCP server. Alternatively pass reserve on booking_options to reserve in one step.

booking_reserve

Get booking form questions for contact details, passengers, and activity-specific fields. Call after experiences_availability with slot details (startTimeId, date, rateId). Pickup/dropoff: include pickupPlaceId and dropoffPlaceId ONLY when places[] was returned as a non-empty array from experiences_detail or experiences_availability; otherwise OMIT both fields (do not send 0 or null). Returns questions.mainContactDetails[], questions.activityBookings[].passengers[].passengerDetails[], questions.activityBookings[].questions (e.g. accommodation), questions.activityBookings[].pickupQuestions[], and options[].questions. Collect ALL required fields before reserving. Activity answers use questions.activityBookings[].questions (numeric questionId). Pickup fields use pickupAnswers with questionId from pickupQuestions. Never use question label text as questionId — always copy questionId from answer_fields or booking_options response. If the user already gave name/email/phone in chat, include contactPrefill and/or the reserve object to create the reservation immediately — do NOT ask the user to contact the MCP server. Otherwise the widget shows the form; then call booking_reserve after answers are collected.

booking_options

Get full details of a specific experience including description, pricing categories, places (pickup/dropoff), offers, and vendor info. If places array is returned, ask user to choose one for pickup/dropoff. Call once per product — do not repeat if the widget already shows this experience.

experiences_detail

Get vendor public profile. Pass vendor_slug from search results (e.g. 'barbaro-tours-morocco') or company name (e.g. 'Barbaro Tours Morocco') — slug is resolved automatically. Returns contact details, location, cancellation policy, and destinations.

get_vendor_info

Get all active products for a vendor. Pass vendor_slug from search results (e.g. 'barbaro-tours-morocco') or company name (e.g. 'Barbaro Tours Morocco') — slug is resolved automatically. Prefer vendor_slug from experiences_search when available.

get_vendor_products

Search for tours, activities, and experiences. For a country or city, prefer location alone — do not add generic query terms like 'things to do' which over-constrain results. Use query for specific activity keywords (castle, food tour, hiking). The query field does not match vendor company names — for a specific operator use get_vendor_products. Returns vendor_slug and vendor_name per result.

experiences_search