Shopping Connectors

---
name: shopping-connectors
description: >-
  When the user wants to shop for, find, compare, or order something, before you
  search for it, so you offer and use their shopping connectors.
---
# Shopping connectors

Two connectors can search and order for the user. Gopuff covers groceries, snacks, drinks, household items, and other everyday goods delivered in minutes. Shop searches products across many merchants, and keeps carts, checkout, and order history for the user's Shop account. A connector is connected when its plugin's MCP tools are among your tools this turn. Once connected, its tools, not the open web, are the place to look for what it sells.
- When the user wants to shop for something, check GetMcpServerStatus for each connector that could plausibly fill the request. For each one that is not installed, offer it once, in one short friendly line, before you search elsewhere: say what it can search and order, and ask if they want to connect it. Offer both in the same line when both fit. Do not offer one again in this conversation if they decline or ignore it.
- If they agree, call InstallPlugin with plugin_id 77083001 for Gopuff or 77565631 for Shop. If it is already installed but its server needsAuth, call AuthenticateMcpServer on that server instead. Never write a link to it yourself: in the app its connect card resumes you when they finish, and elsewhere the result says what to relay.
- When a connector is connected, search it for every shopping request it could plausibly fill, alongside your other ways to search for products rather than after them, and compare what each returns. Read that plugin's own skills and tool descriptions before its first action and follow them for addresses, carts, and orders.
- Name where each result came from, and say plainly when a connector has no match instead of leaving it out. Prices, availability, and delivery depend on the delivery address, so confirm the address before you quote them.
- Searching is free to do on your own, but changing a cart or placing an order is not: ask before you add anything to a cart, and place an order only after the user approves that exact order and its total.
- Some connectors take payment in their own tools: Gopuff quotes an order with get_quote and charges it with place_order. Pay those orders only with a way to pay that the connector's quote lists, such as a payment method saved on the user's account there or cash where offered. Never pay one with a card number, whether from RequestVirtualCard, Shop, X Money, or the Secure Form: those cards are typed into a web checkout page, and a connector order has none. A Stripe Link option on the quote is paid with a one-time Link shared payment token instead, and only while RequestVirtualCard is among your tools, which means Stripe Link is connected; without it, that option can't be paid, so don't pick it. When the user picks it and you have RequestVirtualCard, call it with networkId set to the Stripe network ID in that option's details, the quote's exact total and lines, and the store's website as merchantUrl. Link then asks them to approve the token for that store, and its answer says how to pass the token to the connector's order tool. Never call RequestVirtualCard for a connector order without networkId. When nothing on the quote can pay, say so in one line and give the user the connector's own link to add a payment method or finish in its app, from its tool results. Any other connector order follows the `purchases` skill.
- After a connector places an order, track it until it arrives. When the connector has an order-status tool (Gopuff's is get_order_status), create a routine with UpdateRoutine in the same turn, unless the user said they don't want updates or the latest <automation_status> reminder already lists a routine for this order; when that routine is paused, tell the user it's paused and offer to resume it instead of creating a second one. That reminder lists routines by name, so name it with the connector and the order ID, such as "Track Gopuff order 12345". Give it the schedule "@every 5m": a delivery in progress is time-critical, so the weekday and waking-hours window doesn't apply. A run can't see this chat, so its saved prompt names the connector, the order ID, the status you last saw, and a deadline 3 hours after the order, written as a fixed date and time with its time zone, and it describes each step in words rather than by tool name. Telling the user ends a run, so the saved prompt has each run save or delete first and speak last. Each run first compares the current time with the deadline, whether or not a status check would work: once the deadline has passed, it deletes the routine, then tells the user once that it stopped tracking, with the last status it saw. Otherwise it checks the status: when the status matches the one in the saved prompt, the run stays quiet; when it differs, the run first rewrites only that status in its own saved prompt, keeping the connector, order ID, and deadline exactly as saved, and tells the user the new status in one short line only once that rewrite has saved; when the order is delivered, canceled, or otherwise finished, or the connector says it is no longer tracked, the run first deletes the routine, then tells the user. When the rewrite fails with an error, including an error while reviewing it, the run stays quiet so the next run tries again; when it's refused for any other reason, such as a block or the user declining its approval card, the run deletes the routine, then tells the user once the new status and that updates have stopped. Whenever a delete doesn't save, the run pauses the routine instead before it speaks, and its message adds that the paused routine can be removed from the routine list. When a check fails, including when the connector needs the user to sign in again, the run stays quiet and leaves the routine running rather than pausing it, so the deadline still ends it. Delete the routine whenever the user asks you to stop. A tracking run only reads the order's status and never changes or re-places the order. With the order confirmation, tell the user in one line that you'll send updates until it arrives; if the routine can't be saved, tell them they can ask for the order's status any time instead.
- When the user declines a connector or it cannot fill the request, carry on with the other ways to shop without bringing that connector up again.