Answer product questions
Product questions are answered from the org's connected store, live — prices and stock are read from the vendor at call time, never from a cached copy. Both tools work the same for admin agents and customers' own agents: the catalog is public storefront data, so there is no identity scoping and no email involved.
commerce_search_products— search by product name or SKU. Returns published products with price range, currency, image, and (Shopify) a storefront link.commerce_get_product— one product with its description and variants. PassproductReffrom a search result, orskuwhen the customer quotes one. Each variant carriespriceandavailableForSale.
Only published/enabled products are ever returned — a draft or disabled product behaves exactly like one that doesn't exist. That is deliberate; don't retry looking for it.
Typical flows
- "Do you sell X?" —
commerce_search_productswith the product words the customer used. Present matches with prices; link the storefront URL when present. - "How much is X?" — search, then if the price matters at variant level (sizes, colors), fetch the product and quote per-variant prices. A summary's
priceMin/priceMaxdiffering means the variants are priced differently. - "Is X in stock?" —
commerce_get_productand readavailableForSaleper variant. Answer for the specific variant the customer wants when they've named one.
Reading the results
availableForSale: nullmeans the store doesn't expose stock to this connection (Magento without the CatalogInventory ACL) — say you can't see stock levels, don't guess.priceMin/priceMaxcan be null on Magento search results when the parent product carries no price; the product detail computes the range from its variants instead.- Prices are in the store's own currency (
currency) — don't convert.
Product cards
Products can be shown as cards — image, title, price range and a storefront link, built from the catalog result itself. Where they appear depends on the host:
- Munin's own agent (chat widget and agent inbox): cards render only for the products you pass to
show_products, never for a search on its own. Pass theproductRefof each product your reply is actually about, most relevant first. A search for "black" also returns black watch straps; leave those out. Don't call it when the reply isn't about specific products, for example when you are handing over. The refs must come from a search or product lookup in the same turn. - MCP App hosts: a
commerce_search_productsresult renders as a panel by itself.
That changes what your prose should do:
- Don't restate prices, titles or links the cards already show. Introduce the products and add what the cards can't say ("all three are 20k waterproof", "the middle one is on sale").
- The cards only show fields the catalog exposes. Weights, materials, care instructions and similar specs are not in the product feed: say so plainly and point at the storefront page or
kb_search, rather than inferring them from the title.
When the KB is the better source
The catalog answers what exists, what it costs, and whether it's in stock. Comparison and advice questions ("what's the difference between X and Y?", "which one fits my bike?") are usually better served by kb_search when the org has imported product guides — combine both: facts from the catalog, guidance from the KB.
When to hand over
Nothing here can change the catalog, reserve stock, or place an order. For purchases, restock requests, or price disputes, escalate with conv_request_human.