Skip to main content
Claude has access to 30 ABConvert tools. You don’t call them by name — you describe what you want in natural language, and Claude picks the right one (or chains several together). This page lists what’s possible so you know what to ask for.

​
Discover & resolve

These tools translate names you’d say in English into the IDs that ABConvert needs internally. You almost never trigger these directly — Claude calls them automatically when you mention a product, page, theme, etc. You’ll see Claude make these calls in passing. They never modify anything; they’re read-only lookups against your Shopify catalog.

​
Create a test

Seven test types supported. Each one asks for a hypothesis, primary metric, and traffic split before creating anything.
“Test 10% off the Oxygen snowboard for US mobile visitors”
“Compare 39.99vs39.99 vs 44.99 on the cotton hoodie, 50/50 split”
“Run a price test on all snowboards — minus 15% — but cap traffic at 50% of visitors”
Claude resolves products by name, picks sensible defaults, asks you to confirm, and creates a draft. Variants can be percentage changes, fixed-amount changes, or absolute prices. Price test details →
“Test free shipping over $50 for US visitors”
“Bump my Express shipping rate from 9.99to9.99 to 14.99 in the US zone, 50/50 split”
“Test removing the Standard shipping option in the Canada zone — see what happens to AOV”
Modifies, hides, or adds rates per zone. Untouched rates are auto-preserved (you don’t need to enumerate every existing rate). Shipping test details →
“A/B test my Dawn theme vs the Refresh theme, 50/50”
“Test the new theme I just uploaded against the live one”
Claude resolves theme names. Path-condition routing (testing only on certain URLs) isn’t yet exposed via MCP — use the wizard for that. Theme test details →
“Test the alternate product template I created”
“Compare two product page layouts: the default and the ‘minimal’ template”
Picks alternate Liquid templates by name. Available for any template type (product, index, collection, page, blog, article, cart, search). Template test details →
“Send 50% of /products/old-hoodie traffic to /products/new-hoodie”
“Test a redirect from /sale to /pages/black-friday for US mobile visitors”
Pure URL composition — Claude resolves friendly names (“the sale page”, “snowboards collection”) to real paths. Supports exact match, regex, contains, starts-with. URL redirect test details →
“Test 15% off the whole order against no discount, 50/50”
“Compare free shipping over 50vsaflat50 vs a flat 10 off on all snowboards”
“Test a volume discount — buy 2 get 10% off — on the cotton hoodie”
Builds discount variants against a no-offer control: percentage or fixed amount off products, the order, or shipping, plus volume and threshold tiers. Claude resolves products and collections by name. Offer test details →
“Rename my ‘Test rate 1’ delivery option to ‘Standard Shipping’ at checkout”
“Hide the slowest delivery method for US orders over $100”
“Reorder payment methods so Shop Pay shows first”
Plus-only. Hides, renames, or reorders delivery and payment methods, or adds checkout UI blocks, against an unchanged-checkout control. Checkout test details →

​
Lifecycle: launch, preview, pause, resume, end

Once a test exists (whether you created it via MCP or in the wizard), you can drive it from chat: Deleting a test isn’t available from chat — the API token can’t delete. To remove a draft, end it (if it ever launched) or delete it from the dashboard. Active tests must be ended first either way.

​
Analytics: query results

You don’t need to open the dashboard to check on tests: Available breakdown dimensions: date, device, country, traffic channel, traffic platform, visitor type, landing page, referral domain, and each UTM parameter (source, medium, campaign, term, content). Page-experience tests add page URL, template, and click destination. Pass up to two at once (e.g. device × country).

​
What’s NOT supported (yet)

Still wizard-only:
  • Visual editor tests (DOM mutations like text/image/link changes) — Claude can’t see your storefront the way the visual editor’s click-to-record can.
  • Path-condition routing on theme tests (testing only on certain URLs) — create the test in chat, then add path conditions in the wizard.
We’ll add these as merchant demand drives priority. If you want a specific one prioritized, let support know.

​
What’s NOT supported, period

Some operations are intentionally not exposed:
  • Billing/plan changes — these go through Shopify, not the API.
  • Shop-level settings that aren’t experiment-scoped (CSS, theme injection points, etc.) — wizard only.
  • Deleting tests — the API token can’t delete. End a running test from chat; remove drafts from the dashboard.