Skip to main content
Glama
Sign In
Shopify Theme Inspector MCP

Shopify Theme Inspector MCP

by dragnoir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_profile

Profile multiple Shopify pages in a single call to compare render times and find the slowest pages. Returns a sorted summary for up to 10 page paths.

Instructions

Profile multiple pages on the same store in a single call. Returns a summary comparison of all pages sorted by render time. Useful for finding the slowest pages on a site. Maximum 10 pages per call.

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": {
      "storeUrl": "<storeUrl>",
      "pagePaths": "<pagePaths>"
    },
    "name": "batch_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeUrlYesThe Shopify store URL
pagePathsYesArray of page paths to profile (e.g., ['/', '/collections/all', '/products/my-product'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the output behavior ('Returns a summary comparison... sorted by render time'), a hard limit ('Maximum 10 pages per call'), and the scope constraint ('same store'). It does not explicitly state the operation is read-only, but the profiling context implies it.

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

Conciseness5/5

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

The description is two sentences with no wasted words. It front-loads the primary action, then provides the output, a use case, and a constraint—all in order of relevance.

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

Completeness4/5

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

For a simple 2-parameter tool with no output schema, the description covers the essential aspects: what it does, what it returns, a use case, and a key limit. It lacks explicit return structure details, but the summary comparison is adequately described for agent invocation.

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?

The schema already documents both parameters with descriptions, including an example for pagePaths. The description's 'Maximum 10 pages per call' merely reiterates the schema's maxItems constraint, adding little semantic value beyond what the schema provides. Baseline 3 applies.

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?

The description clearly states the action ('Profile multiple pages on the same store') and identifies the resource ('multiple pages') and output ('summary comparison of all pages sorted by render time'). It distinguishes itself from siblings like profile_page by focusing on the batch/summary aspect, and the use case is explicit.

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 explicitly notes the tool is 'Useful for finding the slowest pages on a site,' which provides a clear use case. However, it does not directly mention when not to use it or name alternatives, though the batch context implicitly contrasts with single-page profiling.

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

Deploy Server

Other Tools