Claude has access to 19 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.Documentation Index
Fetch the complete documentation index at: https://docs.abconvert.io/llms.txt
Use this file to discover all available pages before exploring further.
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.| What you say | What Claude does |
|---|---|
| ”the snowboards collection” | list_shop_collections → resolves to /collections/snowboards |
| ”the cotton hoodie” | list_shop_products → finds the right product GID |
| ”my sale page” | list_shop_pages → resolves to /pages/sale |
| ”the Refresh theme” | list_shop_themes → finds the theme by name |
| ”the alternate product template” | list_shop_templates → lists available Liquid templates |
| ”my US shipping zone” | list_shipping_profiles → returns zone IDs and current rates |
Create a test
Five test types supported. Each one asks for a hypothesis, primary metric, and traffic split before creating anything.Price test
Price test
“Test 10% off the Oxygen snowboard for US mobile visitors”
“Compare 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 →
Shipping test
Shipping test
“Test free shipping over $50 for US visitors”
“Bump my Express shipping rate from 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 →
Theme test
Theme test
“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 →
Template test
Template test
“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 →
URL redirect test
URL redirect test
“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 →
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:| What you say | What happens |
|---|---|
| ”Launch the Oxygen test” | Goes from Draft to Active. Real traffic starts flowing. |
| ”Preview it first” | Goes to Preview status; Claude returns a URL you can open in your browser to QA the variant before launching. Share with the team if you want a second pair of eyes. |
| ”Pause the snowboard test” | Stops assigning new visitors. Existing data preserved. |
| ”Resume it” | Goes back to Active. |
| ”End the test, the variant won” | Closes it permanently. Data stays for analysis; new visitors stop being assigned. |
| ”Delete that draft” | Permanently removes a test. Only works on drafts; active tests must be ended first. |
| ”Update the hypothesis to …” | Patches metadata on a draft (name, description, hypothesis, primary metric). |
Analytics: query results
You don’t need to open the dashboard to check on tests:| What you say | What Claude returns |
|---|---|
| ”How is my Oxygen price test doing?” | Per-variant metrics: views, conversions, AOV, RPV, p-value, confidence interval |
| ”Show me the breakdown by device” | Same metrics, broken out by mobile / desktop / tablet |
| ”Compare the Oxygen and Hydrogen tests” | Side-by-side comparison of both tests’ winners and lifts |
| ”Which variant is winning?” | Plain-language summary with statistical-significance call-out |
| ”Is the snowboards test statistically significant yet?” | Yes/no answer based on the current sample size |
What’s NOT supported (yet)
These test types still require the wizard:- 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.
- Offer tests — not yet exposed via MCP. Offer test details →
- Checkout tests (Plus-only — checkout UI, payment, and delivery customizations) — not yet exposed via MCP. Checkout test details →
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.
- Bulk delete of active tests — safety. End them first, then delete.