Shopify Speed Check

Check Shopify store speed

check_shopify_store_speed

Read-onlyIdempotent

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "check_shopify_store_speed"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`strategy`	No	Which Lighthouse runs to include; defaults to both.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing latency bounds (10 seconds to 2.5 minutes) and a 24-hour cache, both of which affect how an agent should sequence and re-run calls. It also flags that the headless estimate comes with stated assumptions, so the agent knows to qualify that output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then the outputs, then cost/caching; every clause carries information. The first sentence is dense enough that the headless-estimate clause takes a second read, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still tells the agent what will come back (mobile and desktop Lighthouse results, real-user Core Web Vitals, offending apps/scripts, headless delta) plus timing and cache behavior. Nothing essential for deciding to call it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only the strategy parameter is documented in the schema (with its default), leaving url undocumented at 50% coverage. The description implies the URL targets a live Shopify storefront but adds no format or default guidance for the strategy enum, so it neither compensates nor regresses.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: it tests a Shopify store's speed via PageSpeed Insights, surfaces Core Web Vitals and the apps/scripts responsible, and estimates headless impact. That scope is clearly distinct from the fee-calculation and store-detection siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the use case obvious (audit store performance, diagnose slowdowns, compare to a headless build) and the sibling tools do unrelated jobs, so no routing conflict exists. It doesn't state prerequisites such as the store being publicly reachable, which keeps it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Shopify Speed Check tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?