Aisle

Get an aggregate summary of your wedding: total guest counts across all age bands, RSVP breakdown, event count, rooms (totalAccommodations), places (totalPlaces, and emptyPlaces with no active room), registry progress, and more. responded counts attending and declined guests, outstanding counts pending and maybe guests, and responseRate is responded as a percentage of all guests, so a maybe is not counted as a response. Guest identities and individual event answers are not included. Requires authentication.

get_my_wedding_stats

Get full details for a specific wedding vendor including services offered, highlights, FAQs, ratings, and photo gallery. `descriptionStatus` says whether the copy, services and FAQs are `generated` by Aisle from public information or the vendor’s own `listing_content`; a generated listing also carries `contentNote`, and its `priceRange` is null because no vendor gave one. `ratingSource` is `google` for a Google rating. `categorySource` is `aisle_search` when the category is the search Aisle found the business under rather than one the vendor chose.

get_vendor_details

Get full details for a specific wedding venue including highlights, FAQs, travel information, cost estimates, sample timeline, photo gallery, `weddingTotal`, what a wedding for 80 guests costs at the venue (hire, fees, food and drink, rooms extra; `estimate` true for Aisle’s estimate, false for the venue’s own figure; quote it, not a price at the venue’s basis, as the cost of the wedding; null, with `weddingTotalNote` saying why, where the venue cannot hold 80), the fact sheet on record (capacity, rooms, prices, rules, each with its provenance and the quote it was read from; a money row also carries `amount`, its figures as numbers: `low`, `high`, `currency` and `unit`, one of `per_head`, `buyout` (whole property, per night), `venue_fee`, `package`, `per_wedding` or `minimum_spend`) and the awards and memberships the property holds. `costEstimate` is what the venue page shows: beside a price on the fact sheet, Aisle’s older modelled figures and their note are left out, and beside a price the venue stated, so are the total, ceremony and reception line items; `costEstimateLeftOut` names the fields left out, and `costNote` is present only then. `estimators` gives the `destination` to pass to get_budget_estimate and get_guest_travel_estimate for this venue: the budget falls back to the venue’s country when its area has no row, and travel is null when its area has no figures, with `travelInCountry` listing covered destinations in the same country as labelled alternatives. `withheld` names the fields left out because they hold an unreviewed import’s text (`description`, `highlights`, `faqs`, `gettingThere`, `costEstimate`, `sampleTimeline`); it is empty, and `descriptionNote` absent, when nothing was left out. When the slug is not a published venue, `data` is null and `status` says why: `not_found`, with `didYouMean` listing published venues whose name carries the slug’s words or whose slug starts with it, or `delisted`, with `movedTo` (the published listing of the same name, or null) and `nearby` (the closest published venues).

get_venue_details

Estimate round-trip flights and lodging in USD by departure city. Pass guest groups (city + how many). Lodging defaults to the destination's typical stay in a private room per guest; pass nights and guests_per_room to price a different stay or couples sharing, and each group returns its stayNights, rooms and roomRatePerNight. The figures are midpoints of the model's low and high fares and room rates; each priced group carries flightPerGuestRange, roomRatePerNightRange, perGuestRange and totalRange, and the result a totalRange, for quoting a range. A partial total covers only priced groups; report any unpriced guests separately. This model quotes US departure metros only, and coverageNote names the origins it could not price, so relay that limit rather than substituting a US metro. Check urlRestoresEstimate before presenting the web link as a saved result: false means a general starting point that does not restore these guest groups. The MCP equivalent of Aisle's on-site travel estimator.

get_guest_travel_estimate

List all places, including places without rooms, and room details for your wedding. Rooms follow the saved property order. Room date, price and deposit fields are stored overrides; null values may follow the property defaults. The places list supplies each place's id, its position in that order (1 is first), its arrangement (hosted_rooms: rooms the couple hosts and assigns or lets guests choose; room_block: a hotel block guests book themselves; recommended: a suggestion with no rooms held; self_arranged: the couple's own record of a stay booked elsewhere, which no place can be moved onto), stored room-choice overrides, effective modes, its active room count (roomCount), its archivedRoomCount (rooms removed but kept for payment history), and removable, true only when no room of either kind remains, so remove_my_place would take it. A place with archived rooms can never be removed. Requires authentication.

list_my_accommodations

List the events for your wedding (ceremony, reception, welcome dinner, etc.), in date order. date and endTime are UTC instants; localDate and localEndTime are the same times on the wedding's clock, in timeZone. Optionally filter by type, or by a range of days in the wedding's time zone; "total" counts the events returned. Each event's overlapsWith lists the ids of other events on the wedding whose times cross it (an event with no end time is its start), filtered out or not. An all-day item, such as a travel day, has allDay true: its localDate and localEndTime are its first and last days (YYYY-MM-DD), and it overlaps nothing. Requires authentication.

list_my_events

List wedding guests recorded as 13 or older, with contact details and RSVP status. Guests under 13 or with an unknown age band are excluded. Record age bands in Aisle before using these guests in ChatGPT. Optionally filter by status, language or name, and sort by name or by most recent update, RSVP reply or addition. Saved names, contact preferences (a "defaulted" list names any nobody chose), language and timestamps are included. "countsByStatus" counts every listed guest by RSVP status before any filter. Requires authentication.

list_my_guests

List registry and honeymoon fund items for your wedding. Requires authentication.

list_my_registry

List every wedding vendor category with the number of published vendors in each, most first. A category with no vendors (in the location, when one is given) is listed with count 0, so an empty category is told apart from one that does not exist. Optionally filter by location.

list_vendor_categories

List all countries that have wedding venues available on Aisle, with the number of venues in each country, broken down by venue type (types) and by the price band search_venues filters on (priceRanges, with unpriced counting venues a price filter leaves out). Check these before filtering a search by type or price.

list_venue_countries

Put many guests in rooms in one call, from a rule (fill) or a list of rooms and guests (assignments). The server counts beds, keeps households together, skips held-back and full rooms, and returns who was placed and who was skipped, with a reason for each. By default it only plans; show the couple the plan, then call again with dry_run false to place. Up to 200 guests per call. Requires authentication and an Aisle membership.

place_my_guests_in_rooms

Remove a room and its guest assignments from your wedding. The property is kept, even after its last room, unless remove_empty_place is true; otherwise use remove_my_place to explicitly remove an empty property. Use list_my_accommodations to find the room ID first. Cancellation is attempted only after Stripe reports no payment method and no charge; removing a room with a checkout requires confirmed cancellation. Checkout and payment history is retained. Completed or refunded payments, processing payments, and active checkouts with a card entered still prevent removal; a checkout or payment on another room covered by the same household charge can also prevent removal. Explain the returned refusal. Requires authentication and an Aisle membership.

remove_my_accommodation

Remove an empty place from your wedding and its place order, and get back the order that remains (placeOrder names and places {id, name}). Use the places list from list_my_accommodations to find its id. To remove several, pass place_ids instead of place_id: each is removed or kept on its own, and the result lists removed and kept, with the reason each was kept. dry_run: true lists what would be removed and kept without removing anything. This is an explicit removal of the place, including any hotel recommendation or booking link. Places with any rooms, including archived rooms kept for payment history, are refused, and the refusal counts activeRooms (removable first) and archivedRooms (which keep the place for good) apart. Removing a room removes its place only when remove_my_accommodation is called with remove_empty_place. Requires authentication and an Aisle membership.

remove_my_place

Remove an event from your wedding. Use list_my_events to find the event ID first. Returns the removed event as {id, name}. Requires authentication.

remove_my_event

Remove a guest already recorded as 13 or older from your wedding. Use list_my_guests to find the guest ID first. Returns the removed guest as {id, name}. Manage guests under 13 or with an unknown age band in Aisle. Requires authentication.

remove_my_guest

Set the order the places (hotels, villas, houses) read in on the Stay chapter of your guest site, and on the couple's Stays screen. Pass every place at the wedding, first to last, either by id in place_ids (from the places list of list_my_accommodations) or by name in place_names. Ids are safer when two names are close. Passing only some of the places is refused, because the ones left out would have to be given a position nobody asked for. Results and refusals carry the order as places, {id, name} in order, and as placeOrder names, so you can retry. Names match ignoring case and surrounding spaces. Requires authentication and an Aisle membership.

reorder_my_places

Search Aisle's wedding planning guides for advice on budgets, timelines, etiquette, legal requirements, packing, RSVPs, and more. Returns up to 10 relevant excerpts with links to full articles and the date each guide was last revised, at most 3 from any one guide unless max_per_guide says otherwise. When the query names a destination Aisle has a guide for ("Mykonos", "Tulum"), that guide's sections come first. When a word of the query is in no guide, unmatched lists it and coverageNote says the results answer only the rest.

search_guides

Search for wedding vendors by category and location. Categories include photographer, videographer, florist, caterer, DJ, band, planner, coordinator, hair & makeup, cake/bakery, officiant, rentals & decor, stationery, and transportation. Each result carries `descriptionStatus` (`generated` when Aisle wrote the listing from public information and the vendor has not claimed it, `listing_content` when the vendor manages it) `ratingSource` (`google` for a Google rating), `categorySource` (`aisle_search` when Aisle filed the business under the category of the search that found it, `listing` when the vendor manages the listing) and `websiteDomain`, the business’s own site, which often shows a listing filed under the wrong category. `priceRange` is null on a generated listing, whose band was never given by the vendor, so `price_range` matches vendor-managed listings only. `min_rating` and `min_reviews` filter on the Google rating and review count, and `sort` orders by name (default), rating or reviews; most vendors rate 4.5 or more, so the review count is usually what tells them apart. When a location search finds fewer than five vendors, `nearby` lists other locations within 150km holding vendors that match the same category, price and rating filters, with a count and the distance to the closest. A location search also gives each result `kmFromHub`, its distance from the middle of that location’s listings, because `city` names the place searched rather than the vendor’s own town. A result that shares its website or phone number with another vendor in the same category and location lists those vendors in `possibleDuplicates`, each with what they share: they may be one business listed twice, its branches, or one business under two names.

search_vendors

Search for destination wedding venues worldwide. Filter by country, venue type (villa, beach, castle, resort, hotel, estate, garden, restaurant), guest capacity, and price range, and optionally leave out unverified imported listings. Returns venue details with photos and links, and appliedFilters. Each venue’s `weddingTotal` is what a wedding for 80 guests costs there (hire, fees, food and drink, rooms extra): `text` as the venue page prints it, `low`, `high` and `currency` as numbers, and `estimate` true for Aisle’s estimate or false for the venue’s own figure; it is null where neither exists or where the venue cannot hold 80 guests, and `priceRange` is only a band. When fewer than five venues match, relaxed gives the count with each filter removed and excludedUnknownCapacity the venues dropped only because their capacity is unknown; include_unknown_capacity keeps those venues in the results instead.

search_venues

Change the web address of your wedding's guest site, the part after aisle.wedding/. Lowercase letters, numbers and hyphens, two to sixty-three characters. The old address keeps working and redirects, so a link already sent to guests does not break. If the address is refused the result says whether it was already taken by another couple, reserved by Aisle, or not a valid address at all, so you can suggest another. Requires authentication and an Aisle membership.

set_my_site_address

Choose whether the couple assigns rooms or guests choose their own for one Hosted property. List accommodations first for property ids and current modes. Use an id when names repeat. Null clears the override and follows the legacy wedding setting. Requires authentication and an Aisle membership.

set_my_property_room_selection

Edit a room on your wedding, or set its price. Use list_my_accommodations to find the room ID first. Only the fields you pass change; the rest are left alone. Pass null to clear the room type, description, stay dates, check-in and check-out times or check-in notes. To price a room, pass price_unit and price_amount: the unit says what the amount buys ("night" for $180 a night, "room" for the whole stay, "party" once for the household, "head" per guest). "open" lets guests pay what they want, with price_amount as an optional suggestion (or 0 for none): nobody owes anything, the room is theirs either way, and what they give is a gift towards it. Pricing a room turns on payment for it unless you pass requires_payment false; pass price_amount 0 to make it free. The result carries a payability note saying whether guests can pay yet, because a priced room is only bookable once the couple has connected payouts. To let guests pay in two goes, pass deposit_amount with deposit_unit ("amount" for a flat sum, "percent" for a share of whatever the room comes to), deposit_due_date for when the deposit falls due and balance_due_date for when the rest does; guests pay the deposit, then come back and pay the balance themselves, with reminders on each a month out, a week out and on the day. No card is kept and nothing is auto-charged. Leave deposit_due_date off and the deposit reads as due now. A deposit is usually the whole block's term rather than one room's, so set it on every room in the property when the couple describes their villa's billing. A room needs no deposit to have a deadline: pass balance_due_date on its own and the whole price is due by that day, on the guest site and in the same reminders. The changed list in the result names what was written in these input names (check_in_date, price_amount), and "changes" gives each field whose saved value moved as {field, from, to}, with a restated value left out. Requires authentication and an Aisle membership.

update_my_accommodation

Update your wedding settings like partner names, date, location, or venue name, and publish the guest site or take it down. Only the fields you pass change; the rest are left alone. Send null to clear the date, the end date, the location, the venue name or the display name back to empty; the two partner names cannot be emptied, only replaced. Renaming the partners also renames how the couple is named together, unless they have chosen a name of their own, which is left standing and named in the result so you can ask. The result carries a "changed" list of the fields written, in these input names, so a field that could not be stored is never reported as saved; "changes", each field whose saved value moved as {field, from, to}, with a restated value left out; "settings", every field this tool edits as now saved, dates as YYYY-MM-DD; and the resulting "coupleDisplayName", which is the name the site and every other tool result shows them by. Publishing is what makes the site reachable by guests; the address it goes live at comes back in the result. Requires authentication and an Aisle membership.

update_my_wedding

Change an event on your wedding: its name, type, date and time, whether it is all day, venue, dress code or description. Use list_my_events to find the event ID first. Only the fields you pass change; the rest are left alone. Pass null to clear the end time, venue, address, dress code or description. Prefer this over removing an event and adding it back, which drops who was invited and what they chose to eat. The changed list in the result names what was written in these input names (end_time, dress_code), and "changes" gives each field whose saved value moved as {field, from, to}, with a restated value left out. dressCodeGuide is the get_dress_code_guide code and URL the saved dress code reads as, as on add_my_event. Requires authentication and an Aisle membership.

update_my_event

Only guests already recorded as 13 or older can be updated in ChatGPT. Record unknown age bands in Aisle first; this tool cannot change them. Update a guest's details. Use list_my_guests to find the guest ID first. This is how an email address gets onto a guest who is already on the list, which is the usual case for a list imported as names only. Returns saved names, contact preferences (a "defaulted" list names any nobody chose), language and timestamps, including cleared values, and "changed": the fields you sent, by their input names, whose saved value differs from before, so an empty list means nothing moved. Requires authentication.

update_my_guest

Estimate how much alcohol to buy for a wedding bar: total drinks plus a shopping list, wine bottles, beer cans and cases, spirits bottles, and champagne for the toast. Built on the standard planning rule of thumb (roughly one drink per guest per hour, adjusted for crowd and mix) with quantities rounded up to whole bottles and cases, the same math and rounding as Aisle's on-site reckoner, a rule-of-thumb estimate, not a guarantee of consumption. The MCP equivalent of aisle.wedding/tools/wedding-alcohol-calculator.

get_alcohol_estimate

Estimate a whole destination wedding budget by guest count, place and style tier, from Aisle's wedding cost index: modelled estimates in US dollars, not quotes or figures from booked weddings. Pass `destination` (a supported slug) or `country`; the figure matches Aisle's on-site calculator and cost page for the same inputs. A named place the index has no row for is priced at its country and the result says so in `pricedAs`. A place or country the index does not cover returns coverage guidance, never another place's figures. Returns a line-by-line breakdown with a typical total and the low/high range most weddings land in.

get_budget_estimate

Build a wedding-day run-of-show anchored to the ceremony start, hair and makeup through the last dance and send-off, one timed moment per line. Accounts for whether the couple does a first look (portraits move before the ceremony) and how long the reception runs. Times are the standard planner offsets Aisle's on-site reckoner uses, a starting draft to adjust for sunset, venue curfew, and vendors. The MCP equivalent of aisle.wedding/tools/wedding-day-timeline.

get_day_of_timeline

Explain wedding dress codes. Pass a dress code for its definition, what guests wear, what to avoid, and ready-to-paste invitation and wedding-website wording; omit it to list every code in reference order with one-line definitions. Themed labels describe setting or style, so this is not a strict formality ranking. Covers the standard codes (black tie, cocktail, semi-formal) and named ones (vineyard chic, tropical formal, alpine elegant). Each answer links its published guide or the on-site wording tool.

get_dress_code_guide

Generate 15–25 wedding hashtag candidates from the couple's names, surname puns where the names allow them, alliterations, place and year variants, and clean classics. Every tag is CamelCase and deduplicated, ordered best-first by a deterministic quality score (same inputs, same list). Suggestions, not registrations, the couple should still search a tag on Instagram and TikTok before printing it. The MCP equivalent of aisle.wedding/tools/wedding-hashtag-generator.

generate_wedding_hashtags

Compose wedding invitation wording for an exact hosting situation, couple hosting themselves, either set of parents, both families, 'together with their families', divorced parents (stacked correctly, never joined by 'and'), or a couple with children, in four registers from formal to playful. The formal register follows the honour-of-your-presence / pleasure-of-your-company convention based on whether the ceremony is in a house of worship. Call with no scenario to list the options. Etiquette conventions, not rules. The MCP equivalent of aisle.wedding/tools/wedding-invitation-wording.

get_invitation_wording

Get a destination wedding packing list tailored to climate and role. Includes outfits for each event, weather essentials, travel documents, and emergency supplies.

get_packing_list

Get a destination wedding planning checklist organized by months before the wedding. Covers everything from venue booking to day-of logistics.

get_planning_timeline

Split a wedding budget across the three paying parties, the bride's family, the groom's family, and the couple, under a chosen model: traditional American etiquette, an even three-way split, both families equally, or the couple alone. Returns each party's percentage and dollar amount plus the traditional who-pays-for-what reference table. Every dollar figure comes twice: formatted, as $43,200, and as a whole-dollar number in USD (amountUsd, totalBudgetUsd, atThisBudgetUsd). Each figure is rounded on its own, so the parties' amounts can add up to $1 more or less than the total. Traditional assignments are etiquette conventions, not rules, most modern couples adapt them. The MCP equivalent of aisle.wedding/tools/who-pays-for-the-wedding.

get_who_pays_split