MyShoppingPal

Use after find_products to display products and checked shop offers. For broad alternatives, select six distinct eligible models when available; pass up to 24 selected returned productIds in your chosen order. Six appear first with Show more. Pass requestedCount for a top-N request; never fill missing choices. For a gift list, pass items with each returned productId, SKU and recipient label, plus one totalBudget for the whole list; do not pass productIds. For a bundle, pass its returned URL and mainSku; do not pass productIds or items. Repeat the shopper's price, shop, date, variant, purpose, uses and pickup choices, including any city or postcode they supplied. If a necessary choice is missing, pass questionSpec for one compact control and kind for its product category, or one short free-text question. Preserve selected productIds only when one answer can directly reveal those checked choices; otherwise use no IDs and let the model select after the answer. Do not ask fields already supplied. Check pickup stock here. Give only a short sourced reason; do not invent performance or compatibility. Finish without text because the widget is the answer.

show_products

Older name: use find_products and show_products instead. Pass the shopper's own words as query; then call show_products with the returned displayToken. No assistant text: the widget is the answer.

search_products

Product photos, variants and specifications only, when the shopper asks what a product is or looks like. Not for price, deals, delivery or where to buy: use search_products for those. Let the widget show the answer without an introduction or repeated list.

search_catalogue

Use this when a shopper wants to find or compare new electronics by need, budget or exact model in the Netherlands or United States. Read the request for product type, brand and model, price range, exact variant, shops, location, delivery or pickup, and intended use. Put each stated detail in its own field; keep exact names and numbers, and never invent missing details. Do not put words like best or cheap in model-name words. Return matching products with checked shop offer summaries. Use sourced specifications only; do not invent performance or compatibility. Missing price or stock stays unknown, and a sold-out claim needs fresh checks across all requested shops and variants. For a broad product request, ask one useful missing choice through show_products questionSpec before cards: e.g. laptop purpose Work/Gaming/Entertainment or TV purpose Films/Gaming/Everyday. Use kind to retain the requested category. Exact model requests or already supplied answers skip unnecessary questions. The model chooses which question helps; never force a category wizard. If recommendation.question exists, ask that missing choice with questionSpec and no productIds. Use listed common program/game buttons when useful, with allowText for others; use free text only when listed choices would not fit. Do not re-ask supplied or deliberately skipped fields. Otherwise send only matching returned productIds and the same constraints to show_products. The widget gives the answer; do not add text beside it.

find_products