Fudge for Shopify

Get store performance

get_store_performance

Read-onlyIdempotent

Measure the store, or a product, collection, page, article or URL given as subject. metrics returns headline values with their previous period, definition and source. breakdown returns ranked rows such as queries, landing pages, channels, AI assistants, devices, countries, products or discount codes. With neither, returns what exists for the subject. Periods default to the 28 days ending three days ago against the 28 days before. Google Analytics, Search Console and Shopify are separate measurements.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_store_performance"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No
`sort`	No	Breakdown metric to rank by, e.g. clicks, impressions, sessions, revenue, orders.
`limit`	No
`store`	No	The connected store to use. Omit when only one is connected.
`device`	No		all
`offset`	No
`compare`	No
`country`	No	Search Console three-letter country code, e.g. usa.
`endDate`	No
`metrics`	No
`subject`	No	What to measure: a product, collection, page or article ID (product-42 or a Shopify GID), its name or handle, a storefront URL or path (/products/x), or omit for the whole store.
`ascending`	No
`breakdown`	No
`startDate`	No
`comparisonEnd`	No
`comparisonStart`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds value on behavior: metrics carry a previous-period comparison, a definition and a source; the default period is 28 days ending three days ago compared against the prior 28; and GA, Search Console and Shopify are separate measurements rather than blended. That last caveat is important context an agent would otherwise get wrong. It still does not describe result shape or pagination limits.

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-loads the core purpose, then walks through modes, default period, and the data-source caveat in a tight sequence with no filler. Some sentences are telegraphic ('With neither, returns what exists for the subject'), which costs a little readability but not enough to waste space.

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 16-parameter tool with no output schema, the description covers the decisive inputs (subject, metrics, breakdown, default window) and the multi-source caveat, which is the minimum an agent needs to call it sensibly. It leaves ranking, pagination, device/country filtering, and explicit date overrides unexplained, so an agent would have to read the schema for those.

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 only 25% across 16 parameters, so the description carries real weight. It adds meaning for the highest-impact ones: `subject` formats, the `metrics` vs `breakdown` modes and the categories breakdown can return, and the default date window with its comparison period. It says nothing about `sort`, `limit`, `offset`, `ascending`, `device`, `country`, `store`, or the explicit startDate/endDate/comparisonStart/comparisonEnd overrides, leaving much of the surface to the bare schema.

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

Purpose4/5

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

States a specific verb ('Measure') and enumerates the measurable resources: the whole store, a product, collection, page, article, or URL. It also makes the two output modes ('metrics' vs 'breakdown') concrete, so an agent knows what kind of answer to expect. It does not name or distinguish itself from near siblings such as get_store_overview, get_store_insights, or get_keyword_metrics, so it stops short of a 5.

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

Usage Guidelines3/5

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

Gives useful mode-selection guidance: pass `metrics` for headline values, `breakdown` for ranked rows, and neither to see what exists for the subject. That is real when-to-use context for the parameters. However, there is no guidance on when to prefer this tool over the sibling overview/insights/keyword tools, and no exclusions.

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

All Fudge for Shopify tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.