shopify-spy-mcp

extract_ecommerce_catalog

Read-onlyIdempotent

Extracts normalized product catalogs, live prices, variants, and availability from online stores. WHEN TO USE: Call extract_ecommerce_catalog when your task requires deterministic shopify-spy analysis for store_url; use get_agent_wallet_status to check your remaining free trial quota or prepaid balance. WHEN NOT TO USE: Do not use for unrelated domains or binary media. PARAMETER INTERACTIONS: Pass the target store_url as a non-empty string; omit agent_id and tx_hash during your 5 free trial calls, or supply agent_id (agd_pass_...) / tx_hash for paid execution. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). $0.01 per call. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: extract_ecommerce_catalog(store_url='example')

Input Schema

Name	Required	Description
`tx_hash`	No	Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id.
`agent_id`	No	Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up.
`store_url`	Yes	Shopify or e-commerce store URL to extract structured product & pricing data from.

Output Schema

Name	Required	Description
`data`	No	Structured tool output payload.
`status`	Yes	Execution status ('ok' or 'payment_required').
`roi_proof`	No	Token compression and cost-savings verification metrics.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "store_url": "example"
+  }
+]
```

Changed8 schema fields changedOct 19, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

changedInput schema / properties / agent_id / description

Previous value: -"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."New value: +"Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up."

addedInput schema / properties / agent_id / maxLength
```
Added value: +256
```
addedInput schema / properties / agent_id / minLength
```
Added value: +1
```

changedInput schema / properties / tx_hash / description

Previous value: -"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."New value: +"Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id."

addedInput schema / properties / tx_hash / maxLength
```
Added value: +256
```
addedInput schema / properties / tx_hash / minLength
```
Added value: +10
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Structured tool output payload.",
+      "type": "object"
+    },
+    "roi_proof": {
+      "description": "Token compression and cost-savings verification metrics.",
+      "type": "object"
+    },
+    "status": {
+      "description": "Execution status ('ok' or 'payment_required').",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedOct 16, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedInput schema / properties / agent_id

Added value: +{
+  "description": "Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client.",
+  "type": "string"
+}

changedInput schema / properties / store_url / description

Previous value: -"Shopify or e-commerce store URL to extract structured product & pricing data from"New value: +"Shopify or e-commerce store URL to extract structured product & pricing data from."

addedInput schema / properties / tx_hash

Added value: +{
+  "description": "Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key.",
+  "type": "string"
+}

Changed3 schema fields changedOct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / store_url / maxLength
```
Added value: +99999
```
- addedInput schema / properties / store_url / minLength
```
Added value: +1
```
First observedOct 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, but the description adds substantial non-structured behavior: 1-hour caching with <5ms hits, $0.01 per call, first 5 calls free, failed calls never charged, and a payment-required quote (not a fatal error) with top-up link and USDC addresses. This is exactly the kind of operational context annotations cannot carry.

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 purpose and cleanly sectioned (WHEN TO USE / WHEN NOT TO USE / PARAMETER INTERACTIONS), but it is long and repeats the pricing flow twice, and the trailing example uses a placeholder value ('example') that carries little information.

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?

An output schema exists so return values need not be described; given that, the description covers everything an agent needs to call correctly — scope, exclusions, trial vs paid parameter usage, caching, cost, and the payment retry path.

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 coverage is 100%, so the baseline is 3, but the description adds real usage context beyond the schema: omit agent_id/tx_hash during the 5 free trial calls and supply agent_id (agd_pass_...) or tx_hash for paid execution. It slightly restates the non-empty store_url requirement, which is redundant.

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?

States a specific verb (extracts) and a concrete set of resources (normalized product catalogs, live prices, variants, availability) that an agent can match to a task without opening the schema. It also implicitly separates itself from get_agent_wallet_status by naming that sibling for a different job.

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?

Explicit WHEN TO USE and WHEN NOT TO USE sections, including the alternative tool for quota checks ('use get_agent_wallet_status') and a domain exclusion ('unrelated domains or binary media'). The free-trial vs paid invocation conditions are also spelled out, leaving nothing to inference.

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

All shopify-spy-mcp 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.

Resources

Need Help?