Shopify MCP Server

shopify_custom_query

Execute custom ShopifyQL queries to analyze sales, orders, customers, sessions, and marketing data when pre-built tools don't meet specific metric requirements.

Instructions

Run a custom ShopifyQL query for advanced analytics. Use this when the pre-built tools don't cover your specific metric needs. Available tables: sales, orders, customers, sessions, shop_campaign_insights.

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": {
      "query": "<query>"
    },
    "name": "shopify_custom_query"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	A valid ShopifyQL query. Example: FROM sales SHOW total_sales, net_sales GROUP BY product_type SINCE -30d ORDER BY total_sales DESC LIMIT 10

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 19, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool is for 'advanced analytics' and lists available tables, which adds useful context about scope. However, it doesn't disclose important behavioral traits like authentication requirements, rate limits, query execution time, error handling, or what happens with invalid queries. For a custom query tool with zero annotation coverage, this leaves significant gaps.

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 perfectly concise with two sentences that each earn their place: the first states the purpose and usage guidelines, the second provides essential context about available tables. No wasted words, and information is front-loaded effectively.

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?

Given the tool's complexity (custom query execution with no output schema) and zero annotation coverage, the description provides good purpose and usage context but lacks important behavioral details. It doesn't explain what the tool returns, error conditions, or execution constraints. For a powerful analytics tool, more completeness would be helpful despite the concise structure.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents the single 'query' parameter thoroughly. The description adds value by listing available tables (sales, orders, customers, sessions, shop_campaign_insights) which provides semantic context for what can be queried, going beyond the schema's technical requirements. This compensates well despite the high schema coverage.

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 tool's purpose with specific verbs ('Run a custom ShopifyQL query') and resources ('advanced analytics'), explicitly distinguishing it from sibling tools by mentioning 'when the pre-built tools don't cover your specific metric needs.' It also lists available tables, providing concrete scope.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool ('when the pre-built tools don't cover your specific metric needs'), effectively distinguishing it from the many sibling tools listed. It clearly positions this as an alternative for advanced or specific analytics not covered by pre-built options.

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

Deploy Server