Shopify PageSpeed, Core Web Vitals and plan-fee checks for any store, remote MCP.
Score is being calculated.
Compare the monthly and annual cost of Shopify Basic, Grow, Advanced and Plus for a sales volume and payment mix, with break-even sales between plans and requirements only Plus covers. Uses Shopify's published US prices; the variable Plus platform fee is unpublished, so pass plusQuoteMonthly if you have a quote. Only monthlyGmv is required; the rest defaults to one brand fully on Shopify Payments with yearly billing.
| Name | Required | Description | Default |
|---|---|---|---|
| brands | No | Separate brands; each needs its own plan or Plus contract. | |
| billing | No | Billing for Basic, Grow and Advanced. | |
| plusTerm | No | Shopify Plus contract term. | |
| monthlyGmv | Yes | Monthly online sales in USD across all stores. | |
| b2bCatalogs | No | B2B company catalogs needed. | |
| staffAccounts | No | Staff accounts needed besides the store owner. | |
| providerRateBps | No | Third-party provider's own rate in basis points (290 = 2.9%). | |
| sameBrandStores | No | Stores for the same brand, such as regional stores. | |
| plusQuoteMonthly | No | Monthly Plus price from a Shopify quote; replaces the list price. | |
| premiumCardShare | No | Share of Shopify Payments sales on premium cards (0-1). | |
| averageOrderValue | No | Average order value in USD; drives the per-order fixed card fee. | |
| checkoutExtensions | No | Whether checkout UI extensions are needed. | |
| providerFixedCents | No | Third-party provider's own fixed fee per order in cents. | |
| headlessStorefronts | No | Headless storefronts needed. | |
| shopifyPaymentsShare | No | Share of online sales processed by Shopify Payments (0-1); the rest uses a third-party provider. | |
| internationalCardShare | No | Share of Shopify Payments sales on international cards (0-1). |
Test a Shopify store's speed with Google PageSpeed Insights (mobile and desktop) and real-user Core Web Vitals, list the apps and scripts slowing it down, and estimate what a headless build could change, with its assumptions. Takes 10 seconds to 2.5 minutes; results are cached for 24 hours.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| strategy | No | Which Lighthouse runs to include; defaults to both. |
Detect whether a site is a Shopify theme store or a headless Shopify storefront, and which theme it uses. Fetches only the public page; runs no speed test.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds that it fetches only the public page and performs no speed test, which is useful scope information, but it does not disclose authentication needs, rate limits, or error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. The core purpose is front-loaded, and the second sentence adds a precise scope qualifier that earns its place by preventing confusion with the speed-test sibling.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple detection tool with one required parameter, rich safety annotations, and no output schema, the description is nearly complete: it explains what is detected and what is not done. The only gap is the undocumented url parameter, but its name and role are self-evident.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single required parameter 'url' has 0% schema description coverage, so the description carries the full burden. It implies a site URL through context ('a site', 'fetches only the public page') but never states the parameter name, required status, or format, leaving the agent to infer from the schema alone.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (detect) and resource (Shopify theme store or headless storefront, plus theme), and distinguishes itself from the speed-test sibling by explicitly saying it 'runs no speed test.' An agent can tell exactly what this tool does without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: use this to identify Shopify store type and theme, and it explicitly excludes speed testing ('runs no speed test'), which implicitly routes speed testing to the sibling check_shopify_store_speed. It stops short of naming that alternative directly, but the condition for selection is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
calculate_shopify_feescheck_shopify_store_speeddetect_shopify_storeCheck any Shopify store's readiness for ChatGPT & AI shopping agents. Free, no API key, 8 languages.
Lighthouse scores, Core Web Vitals (LCP, CLS, INP/TBT) and top fixes for any URL, mobile or desktop.
Core Web Vitals metrics by CMS, CDN, and framework — free remote MCP, no auth.
Shopify MCP Pack — wraps the Shopify Admin REST API (2024-01)
Add one secure layer between your agents and this server.
