Skip to main content
Glama
Sign In
Shopify Theme Inspector MCP

Shopify Theme Inspector MCP

by dragnoir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_profile_history

View profiling history for a store to track performance trends, showing how render times change over time and measure the impact of optimizations.

Instructions

View profiling history and performance trends for a store. Shows how render times have changed over time. Every profiling call is automatically saved to history. Use this to track the impact of optimizations.

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>"
    },
    "name": "get_profile_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of history entries to return (default: 10)
pagePathNoFilter history to a specific page path. If omitted, lists all profiled pages.
storeUrlYesThe Shopify store URL
clearHistoryNoSet to true to clear history for this store/page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It reveals that profiling calls are auto-saved and that trends are shown, but it omits the destructive `clearHistory` capability, painting the tool as purely view-only when it can delete history. This is a significant under-disclosure for a tool with a mutation side effect.

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?

Three sentences, each earning its place: purpose, detail, and usage guidance. No fluff or repetition. Front-loaded with the core action.

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

Completeness3/5

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

For a 4-parameter tool with no output schema and no annotations, the description covers the primary functionality and use case, but lacks disclosure of the clearHistory side effect and does not describe what the returned history data looks like. These gaps prevent it from being fully complete, though the core viewing purpose is well covered.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds some conceptual context (history auto-save, trend tracking) but does not enrich any specific parameter semantics beyond what the schema already states. The `clearHistory` parameter's destructive nature is not reinforced in the description.

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 opens with 'View profiling history and performance trends for a store' – a specific verb and resource. It clearly distinguishes from sibling tools by focusing on historical trends over time, and adds context with 'Shows how render times have changed over time.'

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 states 'Use this to track the impact of optimizations,' giving a concrete when-to-use scenario. It does not explicitly name alternatives or exclusions, but the use case is clear enough to differentiate from siblings like get_profile_summary or find_slow_templates.

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