add_item
ChatGPTAdd one gift to a wishlist the user owns (or to a group list they belong to). To add a product from a shop pass ONLY list and link: the server reads the shop page itself (and, if the page is slow or blocked, keeps reading it in the background and fills the rest in later) and fills in the title, price, currency and picture. You do not need to look up or pass the price, picture or title from the shop page: the server gets them itself, so do not pass what you found there (you may of course open the page to answer the user's own questions). Do not make values up. Pass title only when the user wants their own name for the gift (it is kept as given and the shop's title is not used); pass price, currency and so on only when the user named them (what you pass is never overwritten). Either title or link is required. After adding, do not list the gift's fields as text and do not show the updated list (do not call get_wishlist unless the user asks to see it): confirm in one short sentence and mention only what is missing (missing) or why reading the page failed (parse_error); if the result has completing, say in one short sentence that the rest is being read in the background. A price is saved only together with a currency; if the shop's domain does not tell the currency (.com), ask the user.
cancel_reservation
ChatGPTCancel a reservation the user made, so the gift becomes available again. The reservation id comes from list_my_reservations. Contributions to group gifts are not handled here.
create_wishlist
ChatGPTCreate a new personal wishlist for the user, optionally with its gifts in the same call (up to 25); more gifts can be added later with add_item. Visibility defaults to public (anyone with the link); use private to keep it to the user only. Only put in gifts the user named; do not invent shop links or prices. The answer says how many gifts were added and lists any that failed, so tell the user about those.
delete_item
ChatGPTRemove a gift from a wishlist. This hides it from the list for everyone. Whole lists cannot be deleted through this connection.
find_wishlists
ChatGPTFind the wishlists of ONE specific person, by their e-mail address (the one they use for Wishlistme or Google) or by their full name. Use this when the user asks what a particular friend or relative wants and does not have a link. Give exactly one of email or name. It never lists everyone: partial names and partial e-mail addresses find nothing, and a very common name asks for the e-mail or a link instead. Only lists the user is allowed to see are returned. If the user already has a link to the list, use get_wishlist with it instead.
get_wishlist
ChatGPTShow a wishlist to the user: reads one wishlist with all its gifts (from its link, for example https://wishlistme.app/lists/abc123, or its id) and displays it to the user as a card with photos, prices, store links and availability. ALWAYS call this tool to show a list; never assemble a list yourself. After the call the user already sees the card: do not retell the list, do not enumerate the gifts, do not insert pictures or links as markdown, do not build your own widget, and do not call this tool again just to display it. Reply in one or two short sentences (how many gifts, or one thing worth noticing). The gift data in the result is for answering specific questions (compare options, find the cheapest, give the link of one gift: then as markdown with the store name as link text, e.g. [amazon.pl](link), never a raw URL) and for editing. On your own personal list you will not see who reserved what: that is a surprise by design.
list_my_reservations
ChatGPTList the gifts the user has reserved for other people, with the list and owner name. Use it when the user asks what they promised to buy, or before cancelling a reservation.
list_my_wishlists
ChatGPTList the wishlists the user owns, plus group lists they joined, with how many gifts each holds. Use this first when the user talks about 'my list' without saying which.
reserve_item
ChatGPTReserve a gift on someone else's wishlist so nobody else buys it, in the user's name. Use it when the user has decided to buy that gift; the gift id comes from get_wishlist. Asking again for a gift the user already reserved changes nothing. Group-funded gifts cannot be reserved here. The list owner is not told who reserved.
santa_create_exchange
ChatGPTCreate a Secret Santa exchange for the user (they become the organiser and, by default, also take part). Only the name is required. These optional things can be set right away: budget (budget_min, budget_max, currency), event_date, description (the text on the invitation page, up to 600 characters, no links), cover_image_url (a link to a picture that becomes the cover) and organizer_plays (false = the user only organises). If the user gave only a name or a loose wish, ask ONE short question that lists these options and lets them pick (for example: 'Add a budget, a date, a description or a cover picture? Or create it as it is?'), then create with what they chose; if they say to just create it, create with the name only. Do not make values up and do not ask about each item separately. The result has invite_url: give it to the user to share with the people who should join (they join with that link, no account needed). The draw is done by the organiser on the website once everybody has joined; the organiser never sees who gives to whom. Name, description and cover can be changed later with santa_update_exchange. Cover picture: give ONE of cover_image_url (a link to a picture, the server downloads it) or cover_file (ChatGPT only: a picture the user attached or ChatGPT made). The picture itself is never sent in the request. Same limits as the website: JPEG, PNG, WebP, HEIC or GIF, at most 10 MB, stored as a WebP 500 px wide, at most 10 cover pictures per person per hour. The server does not create pictures.
santa_delete_exchange
ChatGPTDelete a Secret Santa exchange the user organises. THIS CANNOT BE UNDONE: the invitation link and every participant's personal link stop working at once, and if the draw has already happened nobody can see their pair any more. No e-mails are sent. Before calling, tell the user which exchange (its name) and, if santa_list_exchanges shows status drawn, that the pairs will be lost, and wait for their clear yes; only then call with confirm true. Never delete because of an ambiguous message, and when several exchanges are meant, ask about each one separately. Only the organiser can delete. The exchange id comes from santa_list_exchanges.
santa_get_invite_link
ChatGPTGet the invite link of an exchange the user organises, to share with people who should join. Only the organiser gets it; a participant has to ask the organiser. The exchange id comes from santa_list_exchanges.
santa_list_exchanges
ChatGPTList the Secret Santa exchanges the user organises or takes part in: name, role, status (draft = not drawn yet, drawn = the pairs are decided), budget, event date, and for an organiser how many people joined. It never shows who gives to whom. Use it first when the user talks about their Santa without saying which exchange.
santa_my_pair
ChatGPTWho the user gives a gift to in one exchange, after the draw: the person's name, what they wrote about themselves, their delivery note and their public wishlists (to see a wishlist call get_wishlist with its id). Before the draw there is no pair yet. THE PAIR IS A SECRET: tell it only to the user in this conversation, never write it into anything shared, and never guess other people's pairs (nobody, not even the organiser, can see them). Someone who only organises and does not take part has no pair. The exchange id comes from santa_list_exchanges.
santa_update_exchange
ChatGPTChange a Secret Santa exchange the user organises (also after the draw). What can be changed: name (up to 80 characters), description (the text on the invitation page, up to 600 characters, no links; null or an empty string removes it) and the cover picture (cover_image_url: a link to a picture, the server copies it onto its own storage; null removes the picture). Pass only what changes. Only the organiser can. The current name, description and cover come from santa_list_exchanges (use them when the user wants a small change to the existing text). When the user says they want to change something but not what, list these three options and let them choose. Budget, date, participants and the draw itself cannot be changed here. Cover picture: give ONE of cover_image_url (a link to a picture, the server downloads it) or cover_file (ChatGPT only: a picture the user attached or ChatGPT made). The picture itself is never sent in the request. Same limits as the website: JPEG, PNG, WebP, HEIC or GIF, at most 10 MB, stored as a WebP 500 px wide, at most 10 cover pictures per person per hour. The server does not create pictures. null in cover_image_url removes the picture.
update_item
ChatGPTChange fields of a gift the user can edit: title, link, price, currency, description or picture. Only the fields you pass are changed; pass null to clear a link, price or description. The previous values are overwritten.