EasyRegistry

View saved version →

---
name: add-gifts-to-my-registry
description: Use when a signed-in EasyRegistry owner wants to add gifts to their registry from product links, a shopping list, or a description (including cash-style gifts like a honeymoon fund), or to fix a gift's price, name or details, or remove a gift. Requires EasyRegistry sign-in. Not for buying or contributing to gifts.
---

# Add gifts to my registry

Use this when the user pastes product URLs, names items they want, or asks to change or remove a gift on a registry they own. The user must be signed in to EasyRegistry through the app's OAuth flow.

## Workflow

1. **Pick the registry.** Call `get_my_registries`. One registry: use it and name it. Several: ask which one. None: registries are created on the website; stop here.
2. **Check for duplicates first.** Call `get_my_registry_gifts` and compare against what the user wants to add. If an item already exists, say so and ask before adding another.
3. **Add from links.** For each product URL call `add_gift_by_url`. EasyRegistry fetches the page and reads the name, price and image where it can. Handle links one at a time and report per item: what was added and the price found. If a link cannot be read, fall back to step 4 for that item rather than retrying the same URL.
4. **Add by description.** For items without a link, or cash-style gifts (honeymoon fund, nursery fund, group gift), call `add_gift` with a clear name and an amount in the registry's currency. Ask for the amount if the user has not given one; do not invent prices.
5. **Correct and remove.** Use `update_gift` to fix a name, price, quantity or description on a gift the user has identified. Use `remove_gift` only when the user explicitly asks to remove a specific gift; confirm the gift name first. Both are safe to repeat: an unchanged update or an already-removed gift writes nothing.
6. **Summarise.** List what was added, updated or removed with prices, note anything that failed and why, and remind them the gifts appear on their public registry page.

## Boundaries

- Every write changes what guests see on the public page. For batches of more than five items, show the list and get a yes before adding.
- Never fabricate a price, brand or product name. If `add_gift_by_url` returns no price, tell the user and ask.
- Do not use `add_gift_by_url` on private, login-only or non-product pages; ask for the public product page instead.
- Never touch gifts on a registry the user has not selected in step 1.
- The app cannot purchase, reserve, contribute to, or mark a gift as bought. Guests do that on the public page.
- Never ask for card numbers, bank details or passwords.

## Output

A table or short list of gifts with action (added / updated / removed), price and any note, followed by the public page reminder.

Referenced files: 1

View saved version →

---
name: find-a-registry-and-choose-a-gift
description: Use when someone is a guest looking for a friend's or family member's EasyRegistry gift registry — a wedding, baby shower, birthday or fundraiser — and wants to see what is on it and what is still available. Works without signing in. Not for adding or buying gifts; purchases and contributions happen on the public registry page.
---

# Find a registry and choose a gift

Use this when the user is a guest: "find Sam and Riley's wedding registry", "what's left on Priya's baby shower list", "what can I get them". No sign-in is needed.

## Workflow

1. **Get the two things search needs.** `find_registry` requires the event date (or a close approximation) and at least three characters of the couple's or host's name, or the registry title or slug. Search matches registries within one month either side of the date and will not accept a date more than a month in the past. If the user only has the year or the season, ask for the month.
2. **Search.** Call `find_registry`. It returns up to ten matches. If there is one clear match, continue. If there are several, show title, names and event date and ask which one. If there are none, suggest checking the spelling, the date, or asking the host for the registry link (the slug at the end of the link can be used as the search text).
3. **Show the registry.** Call `view_registry` for the public details: title, event date, location, description and any message from the hosts. Respect the host's settings; if a detail is not returned, do not guess it.
4. **Browse gifts.** Call `view_gifts` and present what is available, grouped sensibly (by price range or category if obvious). Note that some items may already be partly funded or bought; only present what the tool returns as available.
5. **Help them choose.** If the user gives a budget or a preference, filter the list and recommend two or three options with prices.
6. **Hand off to buy.** Give the public registry page link so they can buy or contribute there. The app cannot purchase, reserve or contribute on their behalf.

## Boundaries

- Only use these three public tools; never attempt owner tools for a guest.
- Do not reveal or speculate about the owner's private data (contributions, contributor names, totals, bank details). These tools do not return them.
- Do not fabricate registries, gifts or prices when a search is empty.
- If the registry is password-protected or closed, say so and suggest the guest contact the host.

## Output

The matched registry (title, date, location), a short list of available gifts with prices, and the public page link for purchasing.

Referenced files: 1

View saved version →

---
name: set-up-my-registry
description: Use when a signed-in EasyRegistry owner wants to set up, check or tidy their own gift registry — review its title, event date, location, description, hashtag or thank-you message, see how it is going, or get it ready to share. Requires EasyRegistry sign-in. Not for creating a brand-new registry (that happens on the website) and not for bank or payment details.
---

# Set up my registry

Use this when the user talks about "my registry", "our wedding list", "the baby shower registry" and wants it configured, reviewed or made ready to share. The user must be signed in to EasyRegistry through the app's OAuth flow; if a tool returns an authentication error, ask them to sign in and try again.

## Workflow

1. **Find the right registry.** Call `get_my_registries`. If there is exactly one, use it and say which one you are working on. If there are several, list them by title and event date and ask the user to pick before doing anything else. If there are none, explain that registries are created on the EasyRegistry website (https://www.easyregistry.com.au) and offer to help once one exists. There is no tool that creates a registry.
2. **Show the current state.** Read back the title, event date, location, description, hashtag and thank-you message from `get_my_registries`, and use `get_my_registry_gifts` to say how many gifts are on it. Keep this to a short summary.
3. **Collect changes in one pass.** Ask what they want to change. Gather all the edits (title, description, event date, location, hashtag, thank-you message, open or closed state, notification preferences) before writing.
4. **Confirm, then write once.** Repeat the exact new values back and get a yes. Then call `update_my_registry` once with only the fields that change. Do not call it repeatedly for each field. A repeated identical call is safe and writes nothing.
5. **Report the result.** Confirm what changed and remind them that title, date, location, description and hashtag are visible on their public registry page. If they want gifts added next, switch to the "add gifts to my registry" workflow.
6. **Progress check (optional).** If they ask how the registry is going, call `get_my_registry_stats` for totals and `get_my_registry_gifts` for what is still open, and summarise in plain language.

## Boundaries

- Never ask for, guess or set bank account details, PayID, payment configuration or custom styling. Those are managed on the website only and are not exposed by any tool.
- Do not close a registry unless the user asks for that explicitly and confirms.
- Do not invent dates or locations. If a value is unclear, ask.
- Do not claim a registry was created, paid out, or shared. The tools only read and update settings.
- Contribution details from `get_my_registry_purchases` are the owner's private data; never repeat them into a message intended for guests.

## Output

A short confirmation of the registry worked on, the fields changed with their new values, and the next suggested step (add gifts, or share the public page).

Referenced files: 1