GuruWalk MCP Server

Check real-time availability for one or more tours or activities on GuruWalk in a single call. Pass an `items` array — each entry is independent and has its own type, product_id and date range. Returns a `results` array where every entry echoes its `type` and `product_id` so you can match each response to its request. Check the tours the traveler has already chosen — this is not a catalog browsing tool, so don't run it over search results to explore what's on offer. For paid activities, shows rates by traveler type (adult, child, infant). `price` is always per person — never state a group total by quoting `price` alone. When `total_price` is present on a rate, it's already computed for the participants you requested of that rate's type — quote it directly, don't multiply or divide it yourself. If the group mixes traveler types (e.g. adults and children), sum each rate's `total_price` for the full group total. For free walking tours, no upfront price — travelers pay what they want after the tour. For paid activities, an event's `languages` lists the languages that session runs in (e.g. audioguide languages), and sessions differing only in language are merged into a single event; free walking tour events each carry a single `language` instead. `booking_url` is returned once per item, not per event; for paid activities you can add a `date=YYYY-MM-DD` query parameter to preselect a day. Maximum date range per item: 5 days. Per-item errors (invalid dates, product not found) are reported inside that item's result without failing the rest of the batch. Use this tool when the traveler asks about specific dates, wants to know if something is available, or is ready to book. When the traveler hasn't given specific dates, use the booking date ±2 days as the default search range. Supports en, es, de, it; any other value falls back to English. Pass the traveler's language code anyway and translate the answer into their language.

Get the full detail of one or more tours or activities on GuruWalk in a single call. Pass an `items` array — each entry has its own type, product_id and language, and is processed independently. Returns a `results` array where every entry echoes its `product_id` and `type` so you can match each response to its request. Always batch when you need details for several tours (e.g. before recommending or comparing them): send them all in one call instead of invoking this tool several times. Each successful entry returns description, images, reviews, duration, available languages, cancellation policies, and meeting point info. Paid `product` entries also return `highlights`, `included`/`excluded`, `pricing_from`, and `where` (address + coordinates). `free_tour` entries return `itinerary` as a flat array of point-title strings (no descriptions), plus `guide.name`, `meeting_point_url`, and `how_to_find_me`. Both types return `meeting_point_url` (Google Maps link) whenever the meeting point has coordinates. For a `free_tour` that is the meeting point. For a paid `product` it is the reference point published on the listing: useful to orient a traveler who has not booked yet, but the operative meeting point of a purchased activity — with the supplier's own instructions — is the one in its voucher. Offer it as a reference, never as the confirmed meeting point of a booking. Paid `product` also returns the address text and coordinates in `where`; `free_tour` also returns `meeting_point_latitude` and `meeting_point_longitude` (use these coords as destination for routing), plus `how_to_find_me`: a free-text note written by the guide describing how the traveler can recognize them at the meeting point. Per-item errors (product not found) are reported inside that item's result without failing the rest of the batch. Use this tool whenever the traveler asks what a tour covers, which places it visits, its itinerary, route, description, meeting point, duration, or any content-related question. For the meeting point of a paid activity the traveler has already booked, the booking's voucher comes first; fall back to this tool only when that voucher has no meeting point yet, and say then that this is the point published on the listing and that the definitive one arrives with the voucher. Always call this tool BEFORE answering questions about a specific tour — never give generic opinions or advice without consulting the real data first. Supports en, es, de, it; any other value falls back to English. Pass the traveler's language code anyway and translate the answer into their language. Each result includes the tour's url — when recommending or confirming a tour, share it so the traveler can open it to book.

Browse tours and activities within a specific category for a destination on GuruWalk. Categories include free walking tours, food tours, bike tours, day trips, skip-the-line tickets, and more. Returns listings with ratings, verified review counts, duration, available languages, and pricing. Use the category IDs returned by search_tours_activities_by_destination — never invent category IDs. Use this tool to dive deeper into a specific category that matches what the traveler has shared (e.g. food tours for a foodie, night tours for someone asking about evenings, kid-friendly activities for families). Supports en, es, de, it; any other value falls back to English. Pass the traveler's language code anyway and translate the answer into their language. Each product includes a booking_url — when recommending tours, share it so the traveler can open the tour to see details, prices and book.

Search a city to explore free walking tours and paid activities on GuruWalk, the world's largest free walking tour platform. Returns destination info, tour categories (free tours, food tours, day trips, tickets, and more), and featured listings with ratings and verified traveler reviews. Covers 1,000+ cities worldwide. Free tours operate on a pay-what-you-want model. Supports English, Spanish, German, and Italian (en, es, de, it); any other value falls back to English. Pass the traveler's language code anyway and translate the answer into their language. Use this tool when the traveler asks what to do, what to see, or what tours or activities are available in a destination, or wants help planning their trip or days there. Do not call it when the destination is only mentioned in passing with no request for plans or recommendations. If the traveler mentions a landmark instead of a city, infer the city (e.g. 'eiffel tower' → Paris, 'colosseum' → Rome, 'sagrada familia' → Barcelona, 'big ben' → London). After getting results, review the categories and featured_products to find the most relevant matches for what the traveler asked about. Each featured product includes a booking_url — when recommending tours, share it so the traveler can open the tour to see details, prices and book.

Present a selection of tours or activities to the traveler as a visual list of cards (photo, rating, price, booking button) rendered inline in the conversation. Showing cards is the default way to present tours to the traveler: whenever your reply features specific tours (recommendations, a shortlist, availability results), call this tool alongside your text instead of waiting to be asked. Don't re-render a selection you already showed unless it changed. Call it AFTER finding tours with the search tools — it is a presentation tool, not a search tool. If you already checked availability with get_product_availability, you can pass each item's sessions (date and start time) and the cards will highlight them with booking links preselecting the date. For clients without UI support the same data is returned as structured text.

Returns an official GuruWalk support guide for a specific traveler-support topic. GuruWalk is a platform for free walking tours and paid activities; these guides are GuruWalk's own source of truth on how bookings, cancellations, account settings and contacting guides actually work, including current policies and the exact URLs travelers should use. These guides apply only to bookings and accounts on guruwalk.com. Available topics: - account_settings: The traveler wants to manage their GuruWalk account: edit their details (name, surname, phone, city, password), change their email, stop receiving emails / unsubscribe, or delete their account; or they can't access their account. These are concrete steps you shouldn't improvise: consult this before answering. - contact_guru: The traveler wants to contact or coordinate something with the guide of their GuruWalk booking, or thinks they are talking directly to the guide: they can't find them at the meeting point, the guide didn't show up, they're running late, they treat you as if you were the guide, ask for the tour photos, or ask about bringing a pet or paying the guide, or have a question only the guide can answer. - free_tour_modification: The traveler wants to modify or reschedule their GuruWalk free tour — change the day, time, language or number of people — or asks how to do it. - group_booking: The traveler wants to book or extend a GuruWalk booking for a group (they usually say how many; treat it as a large group from around 6 people), asks how to book for many people, can't book for the whole group, sees a large-group notice or is asked for a card or payment for the group, or had a booking cancelled as "group or duplicate". The rules aren't intuitive; consult this before advising. - paid_cancellation: The traveler wants to cancel or change a paid activity booked on GuruWalk, asks about a refund, or can't cancel from their account. Call this when the traveler raises a support topic covered above. Pass the exact topic; the guide content is returned.