Перейти к содержанию

tickadoo — билеты и экскурсии

Подбор и бронирование экскурсий, спектаклей и развлечений в городах мира

Доставка и логистикаавтор: tickadoo · добавлен каталогомБесплатно✓ Проверен модератором
23 инструмента
подключить к ассистенту

Добавьте сервер в «Мои MCP» — получите адрес подключения для Claude и ChatGPT.

Добавить в «Мои MCP»

Нужно войти или зарегистрироваться — вернём на эту страницу.

/about

Описание

Каталог билетов на театр, достопримечательности, туры и другие развлечения в сотнях городов. Пригодится путешественникам и тем, кто ищет, чем заняться в своём городе. Можно искать впечатления по городу, категории, месту или координатам, получать подборки на сегодняшний вечер, на ближайшие часы и на неделю, идеи для семейного дня или свидания, малоизвестные места и варианты под настроение. Сервер составляет обзор города и кандидатов для многодневного маршрута, сравнивает несколько предложений, показывает подробности, похожие варианты, реальную доступность дат, время и цены, а также подсказывает, как добраться из аэропорта или с вокзала. Сервер публичный, ключ не нужен.

/tools

Инструменты · 23

из ответа tools/list

check_availability

Use this when the user has picked a specific experience and asks about exactly one date: whether it is available that day, what it costs for a party, or a booking link for that date. For browsing a date range or listing upcoming times and live slot prices, use get_availability.

check_availability(date: string, slug: string, format?: string, language?: string, party_size?: integer)

compare_experiences

Use this when the user wants a side-by-side comparison of 2-5 specific products. Pass the slug for each. Returns a comparison table plus per-axis winners (value, rating, popularity, family-fit).

compare_experiences(slugs: array, format?: string, language?: string)

find_nearby_experiences

Use this when the client already holds exact latitude and longitude coordinates and wants experiences near that point. When only a place name, landmark, or neighbourhood is known, use search_local_experiences, which accepts coarse place hints and needs no coordinates.

find_nearby_experiences(limit?: integer, format?: string, category?: string, language?: string, latitude: number, longitude: number, radius_km?: number)

get_availability

Use this when the user is ready to check live bookable dates, times, prices, or remaining spaces for one selected product. This is the live supplier-check tool; pass product_id from search or slug plus city_slug. Slot price.amount is in MINOR currency units (pence/cents): amount 13125 with currency_code GBP means GBP 131.25. Slot time is venue-local; when the venue timezone is known, timezone carries its IANA name and datetime/next_available carry the real UTC offset (e.g. 2026-07-18T19:30:00+02:00), so they are safe for time math.

get_availability(slug?: string, as_of?: string, fresh?: boolean, date_to?: string, city_slug?: string, date_from?: string, party_size?: integer, product_id?: string, preferred_time?: string, idempotency_key?: string)

get_city_guide

Use this when the user wants an orientation overview of a city for trip planning. Returns a ranked list of the city's most popular bookable experiences (search rows); derive the dominant categories and price levels from those rows rather than expecting a structured guide payload.

get_city_guide(city: string, format?: string, language?: string)

get_date_night

Use this when the user wants an evening for two. Returns a flat ranked list of experiences (search rows) with romantic-tagged rows promoted and out-of-season products dropped, not a structured pre-dinner/dinner/show arc. Promotion is a re-rank, not a filter, so rows are not guaranteed couples-only. `date` selects which season counts as current; `budget` is accepted but NOT yet applied. Compose the evening yourself (search_by_mood with mood 'romantic' can bias the pool further).

get_date_night(city: string, date?: string, budget?: string, format?: string, language?: string)

get_experience_details

Use this when the user selects a specific experience from search results and needs richer product, location, supplier, and booking fields. Accepts either product_id or slug.

get_experience_details(slug?: string, format?: string, language?: string, product_id?: string)

get_family_day

Use this when the user wants family-suitable options for a day in one city. Returns a flat ranked list of experiences (search rows) with family-tagged rows promoted and out-of-season products dropped, not a structured morning/lunch/afternoon/evening plan. `date` selects which season counts as current; `kids_ages` and `budget` are accepted but NOT yet applied, so compose the day yourself and verify age suitability per pick via get_experience_details.

get_family_day(city: string, date?: string, budget?: number, format?: string, language?: string, kids_ages?: array)

get_hidden_gems

Use this when the user wants lower-profile options rather than headline bestsellers. Excludes Bestseller, hop-on-hop-off, and CityPass tagged products and prefers highly rated rows with fewer reviews; falls back to the standard ranked list when a city has too few qualifying rows (results may then overlap with headline search).

get_hidden_gems(city: string, format?: string, language?: string, max_results?: integer)

get_last_minute

Use this when the user wants something to do within the next few hours. Returns currently-on-sale experiences with seasonal products filtered out, ranked by popularity. Rows may include start_time, countdown_text, and seats_remaining hints when known, but none are guaranteed: confirm the selected experience with get_availability before stating it starts soon or is available today.

get_last_minute(city: string, hours?: integer, format?: string, language?: string, latitude?: number, longitude?: number)

get_related_experiences

Use this when a widget or client holds a selected product_id and needs related products to pair with it, do after it, find nearby, or find similar alternatives. Returns cached graph and semantic related products for trio-style widgets.

get_related_experiences(format?: string, context?: string, language?: string, product_id: string, max_results?: integer)

get_transfer_info

Use this when the user is arriving in a supported city and needs transfer guidance from an airport, station, or port to a hotel coordinate. Returns taxi, metro, bus, and train estimates with durations, costs, and directions.

get_transfer_info(city: string, format?: string, language?: string, from_type: string, to_latitude: number, to_longitude: number)

get_travel_tips

Use this to surface bookable experiences relevant to a practical topic in a city, such as transport passes or food tours. It returns a ranked list of experiences (search rows) ONLY: the topic filter is accepted but not yet applied, and the payload contains no tips text, emergency numbers, or phrases. Do not rely on it for actual logistics guidance; answer those questions yourself and use this list for bookable add-ons.

get_travel_tips(city: string, topic?: string, format?: string, language?: string)

get_whats_on_this_week

Use this when the user wants ideas for the coming week in a city. Returns a ranked list of currently on-sale experiences (search rows) with out-of-season products dropped, not a day-by-day calendar. Assemble any weekly structure yourself and verify specific dates with get_availability.

get_whats_on_this_week(city: string, format?: string, language?: string)

list_cities

Use this when the user wants to browse supported cities before searching. Returns city names, slugs, country codes, and product counts.

list_cities(limit?: integer, format?: string, country?: string, language?: string)

plan_itinerary

Use this when the user wants a multi-day plan for a single city. Returns a flat ranked candidate list of experiences (search rows), not structured day slots or a running cost. Arrange the candidates into days yourself and compute totals only from returned price fields.

plan_itinerary(city: string, days: integer, pace?: string, budget?: string, format?: string, audience?: string, language?: string, interests?: string)

recommend_experiences

Use this when the user describes what they want in natural language rather than naming a category. Parses the query for audience, mood, constraints, occasion, and time of day, then returns scored recommendations with a reason field explaining the match.

recommend_experiences(pax?: integer, city?: string, date?: string, limit?: integer, query: string, format?: string, language?: string)

render_experience_cards

Use when visual cards would help present a discovery result from a supported search tool. Pass the product_id values from that result as experience_ids, never full product rows, and choose a render_type. Optionally pass render_context.intent_summary (a short phrase describing what the user asked for, such as city, date, or audience) to set the heading. Keep each result set to one card view to avoid duplicate cards; concise text context may accompany it.

render_experience_cards(render_type: string, experience_ids: array, render_context?: object, idempotency_key?: string)

report_quality_signal

Use this to push a quality signal back to tickadoo about an experience or recommendation you previously surfaced. Examples: stale availability, a failed click-through, a supplier outage, or misleading content. Requires a real forward-event request_id returned within the last 30 days. Repeating the same signal for the same request is idempotent per caller.

report_quality_signal(notes?: string, request_id: string, signal_type: string)

search_by_mood

Use this when the user describes the feeling or vibe they want rather than a category, such as romantic, relaxing, adventurous, family fun, foodie, luxury, or rainy day. Maps the mood to preset search filters and returns matching experiences.

search_by_mood(city: string, mood: string, limit?: integer, format?: string, language?: string)

search_experiences

Use this when the user names a city plus a category, query, or filter set and wants a ranked list of bookable experiences. `query` matches on experience NAME (and venue), so it suits a title or keyword ("Lion King", "river cruise"); for mood or theme use search_by_mood, and for a free-text "what should I do" ask use recommend_experiences. When a query matches no name, results are the city top-picks flagged match_type "fallback_city_ranked" (reason_codes include "fallback_no_text_match") rather than a genuine match, so treat those as suggestions, not the thing asked for. Returns products each with a stable product_id, plus name, slug, city, category, price, rating, review count, and tags. To show the results as visual cards, pass the product_id values from these results into render_experience_cards (experience_ids). Pair with get_experience_details for richer fields.

search_experiences(city?: string, tags?: array, limit?: integer, query?: string, format?: string, category?: string, language?: string, max_price?: number, min_rating?: number, popular_only?: boolean, indoor_outdoor?: string, min_review_count?: integer, restrict_to_top_rated?: boolean)

search_local_experiences

Use this when the user mentions a place, neighbourhood, landmark, or area but does not give exact coordinates. Examples: 'near the Louvre', 'in Trastevere', 'around Times Square', "walking distance from St Paul's Cathedral". Returns experiences matched first by exact venue/neighbourhood, then by city centre fallback. Do not use for general city-wide search; use search_experiences for that.

search_local_experiences(city?: string, tags?: array, limit?: integer, format?: string, date_to?: string, language?: string, date_from?: string, place_hint: string, radius_hint?: string, neighbourhood?: string)

whats_on_tonight

Use this when the user asks what is on in a city tonight. Returns evening-appropriate experiences currently on sale, with out-of-season products filtered out, evening-led options ranked first, and multi-day passes, travel cards and transport products ranked last. Top results carry start_time (venue-local) when the live supplier calendar confirms a performance in the evening window (late afternoon onward); a confirmed slot lifts a row, and timed rows sort soonest-first within one relevance band. Rows without start_time have no confirmed evening time. Confirm the selected experience with get_availability before stating it is bookable tonight.

whats_on_tonight(city: string, format?: string, category?: string, language?: string, max_results?: integer)

Вопросы, новые серверы, обсуждение MCP

t.me/rusmcp · t.me/RusMcp_bot