ResourcesPlatform
Shopify storefront AI tools: what to inspect before trusting an answer
Shopify's WebMCP tools give compatible visiting agents a way to work with the storefront. Tool availability, the data returned and the answer a shopper receives are separate things to verify.
Updated 4 min read
If you maintain a specialist catalog, the useful test is concrete: can an agent answer an important question about the right product using the facts you maintain? A storefront tool list helps you investigate that question. It is not a score for how well AI shopping works on your store.
What Shopify provides
Shopify announced WebMCP support on 5 August 2026 for Liquid storefronts and the Hydrogen developer preview, without a merchant installation step. Its launch notice identifies Chromium support through an origin trial. This is a dated platform statement, not evidence that a particular shopper used the tools. Shopify announcement.
Shopify currently documents ten storefront tools, grouped below. The tool list changes when an eligible checkout replaces the storefront tools. Shopify storefront WebMCP reference.
Scroll sideways for columns out of view. Keyboard: focus the table and use the Left and Right arrow keys.
| Job | Tool names |
|---|---|
| Search, browse and select products | search_catalog, browse_store, get_product, show_variant |
| Read or change the cart | get_cart, update_cart, cancel_cart |
| Checkout and order navigation | proceed_to_checkout, manage_orders |
| Store policies and FAQs | search_shop_policies_and_faqs |
Checkout has its own tool list
On 28 September 2026, Shopify announced WebMCP support for checkout. On an eligible checkout page, the browser can register four separate tools: get_checkout reads the current state; update_checkout changes supported fields; complete_checkout places an order after the buyer confirms it; and navigate_to_storefront returns to the store when it has an online storefront. Shopify says the tools run in the buyer’s checkout session without merchant configuration. Checkout WebMCP documentation.
After proceed_to_checkout, refresh the tool list on the checkout page. If checkout tools are unavailable, the buyer completes checkout on the page. The new tools extend Shopify’s native browser route; they do not establish that a particular consumer assistant uses it. StoreKnows’ additional tools remain read-only product-answer tools and do not operate checkout.
For a product-answer investigation, start with the catalog tools. Shopify describes get_product as including variants, prices and in-stock option combinations; show_variant handles a variant or partial option selection. Test that native capability before assuming a custom variant tool is necessary.
Cart and navigation tools can affect the current session. For an initial diagnostic, inspect product-reading operations and avoid unrelated cart or checkout actions.
Keep browser and server tools separate
WebMCP is a proposed standard for website tools. Chrome’s documentation includes an origin trial, a local testing flag and a tool-inspector extension. The inspector is separate from Gemini in Chrome. Chrome WebMCP guide, checked 13 September 2026.
Shopify’s migration guide, checked 2 October 2026, says UCP replaced the server-side Storefront MCP catalog and cart tools. That server route remains separate from WebMCP in a browser session. Neither route establishes what an ordinary consumer-assistant conversation uses.
Record the client and browser, configuration and date. If an API only appears after enabling a development flag, label the result accordingly. Do not turn that setup into a claim about normal shopper availability.
This article does not estimate shopper adoption, certify named consumer-client support or predict an origin-trial expiry. Those require current evidence about the actual client and deployment.
Inspect what the tool returned
Use Chrome’s current inspector guidance rather than a console snippet from an older API draft. Keep the browser version and experimental settings with the answer log.
Illustrative question: “What is the input connector on adapter AX-4, and how does it differ from AX-4B?” Inspect the exact request and returned model/values, then the answer. A tool that was not called, a called tool missing the fact, and an answer misreading a returned fact are different findings. If the response is unavailable, keep that cause unresolved.
The product-data trace follows this source-to-answer chain. Do not reorder working variants or rewrite titles on one unsupported explanation.
Decide whether another tool is justified
If native tools answer well, retain that result. Correct wrong source facts first. For an AI-channel issue, inspect the channel’s sources instead of assuming a browser embed changes them.
A supported additional tool merits testing when it addresses a reviewed browser-route gap. Use the before-and-after method to distinguish preview, publication, availability and answer quality. StoreKnows tools use a saved catalog copy and require an agent to choose them; they are not live inventory. Shopify’s framework support does not establish StoreKnows compatibility.
Next step: inspect one native response for your question. How the StoreKnows check works explains when its catalog-built baseline and supported proposals may help.
Corrected 13 September 2026: removed unsupported client-adoption, trial-expiry and opt-out assertions, universal native-data limitations, historical accuracy headlines and variant-reordering advice. Updated 30 September 2026 to distinguish checkout tools from the ten storefront tools; revised 2 October to link shared recording and comparison guidance. No new storefront test is reported.
StoreKnows is independently developed and not affiliated with, endorsed by or sponsored by Shopify, OpenAI, Google or Anthropic.
Inspect the documented tool route
Check current documentation and the actual tool response for the storefront and agent configuration you are testing.
Open Shopify's storefront WebMCP referenceQuestions this article answers
- Does having WebMCP tools mean consumer assistants use them?
- No. Confirm the specific client, browser and session, and inspect whether a tool was called. An available tool list does not establish adoption or what an unrelated consumer assistant receives.
- How should I investigate a missing product detail?
- Compare the exact question and product identity with the actual request, returned content and maintained reference. A missing field in one response is a scoped observation, not proof of a universal platform limitation.