← List2CartCONTENT HISTORY
WHAT CHANGED
Update to List2Cart
Snapshot Nov 16, 2026 · 18:17 UTC · version 0.1.3
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save List2Cart and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user wants to turn meal planning, recipes, events, or other conversation decisions into a shared List2Cart shopping list, or manage an existing List2Cart list URL.",
"included_files": [],
"name": "list2cart-shopping",
"skill_md_contents": "---\nname: list2cart-shopping\ndescription: Use when the user wants to turn meal planning, recipes, events, or other conversation decisions into a shared List2Cart shopping list, or manage an existing List2Cart list URL.\n---\n\n# List2Cart shopping workflow\n\nUse the List2Cart MCP tools for shopping-list operations. The service is intended for shared household lists and does not require user login.\n\n## Privacy and data minimization\n\n- Do not send conversation transcripts, personal discussion, recipe narratives, event descriptions, or unrelated context to List2Cart.\n- Send only the list name, product names, quantities, extension days, and list URL as needed by the tools.\n- Extract only items the user has decided to buy or explicitly asks to add. Do not infer optional ingredients or unrelated products without making them clear to the user.\n- Preserve quantities and units. If quantity is unknown, omit it rather than inventing one.\n- Treat list URLs as user-provided access references. Use them only for the requested list operation and do not expose them to unrelated services.\n\n## Create a list\n\nWhen the user asks to make a shopping list from the current conversation:\n1. Identify a concise, useful list name (for example, a meal name or event name).\n2. Extract only the agreed purchase items and their stated quantities.\n3. Call `create_shopping_list` with the list name and item names/quantities according to its advertised schema.\n4. Return the resulting List2Cart URL and explain that opening it and completing registration activates the list for 30 days, as described by List2Cart.\n5. Do not claim the list was created unless the tool confirms success.\n\n## Add items\n\nWhen the user provides a List2Cart URL and asks to add products:\n1. Use `add_shopping_list_items` with that URL and only the requested product names and quantities.\n2. Confirm the additions only after tool success.\n\n## Read a list\n\nWhen the user asks what is on a List2Cart list, or asks about assignments, budget usage, or remaining time:\n1. Use `get_shopping_list` with the supplied URL.\n2. Summarize only the returned list data. Do not infer a person's assignment or remaining budget if it is absent.\n\n## Extend expiry\n\nWhen the user explicitly asks to extend a list:\n1. Confirm the requested extension duration if it is ambiguous.\n2. Use `extend_shopping_list` with the supplied URL and requested number of days.\n3. Report the new expiry only if returned by the tool.\n\n## General behavior\n\n- If the URL is missing for an operation on an existing list, ask the user for it.\n- Never create, add, or extend a list merely because shopping items were discussed; wait for a clear request to make or manage a list.\n- Batch items into as few tool calls as practical.\n- The tools are described as non-destructive, but still require user intent for write operations.\n- If a tool returns an error or incomplete result, state that plainly and do not fabricate a URL or result.\n"
}SHA-256 of public snapshot: 3db374beb284167d58822ff7c35df3f6972e0489f2496d94d656f91b910ddd76