Aisle

List accommodation options for your wedding. Requires authentication.

list_my_accommodations

List all events for your wedding (ceremony, reception, welcome dinner, etc.). 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 or search by name. Requires authentication.

list_my_guests

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

list_my_registry

List available wedding vendor categories with the number of vendors in each. 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.

list_venue_countries

Remove a room and its guest assignments from your wedding. 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 event from your wedding. Use list_my_events to find the event ID first. 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. 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 by name, first to last. Use list_my_accommodations to read the current order from its placeOrder list, then send that list rearranged: passing only some of the places is refused, because the ones left out would have to be given a position nobody asked for. A refusal carries the current order back 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 relevant excerpts with links to full articles.

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.

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. Returns venue details with photos and links.

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

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. 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). 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. 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 what was written, so a field that could not be stored is never reported as saved, 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, 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. Prefer this over removing an event and adding it back, which drops who was invited and what they chose to eat. 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. 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 destination wedding budget by guest count, destination, and style tier. Pass `destination` (a supported slug) for a figure that matches Aisle's on-site reckoner exactly, a starting worksheet using illustrative destination allowances, not measured averages or supplier quotes. Unsupported destination requests return coverage guidance, not a generic budget. Omit destination and pass `country` for a rougher regional estimate in USD. Returns a category breakdown with a typical figure and a low/high range when covered.

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 from most to least formal with one-line definitions. Covers the standard codes (black tie, cocktail, semi-formal) and named ones (vineyard chic, tropical formal, alpine elegant). Each answer links the page it came from under aisle.wedding/wedding-dress-codes.

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. 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