Skip to main content
Glama
mcp-public-intel

mcp-public-intel

by pecopeko

shopify_store_catalog

Fetch a Shopify store's public product and collection feeds to inspect variants, prices, discounts, SKUs, and stock status without an API key.

Instructions

Fetch public Shopify store catalog feeds (/products.json and /collections.json) with variants, min/max prices, compare-at discount percentages, SKUs, and stock status. Zero API key required.

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": {
      "store_url": "<store_url>"
    },
    "name": "shopify_store_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of products to return (1-100, default 25).
store_urlYesPublic Shopify store domain or URL (e.g. 'allbirds.com' or 'https://gymshark.com').
collection_handleNoOptional collection handle (e.g. 'best-sellers') to scope products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description bears the full burden, and it does contribute real behavioral context: these are public feeds requiring no credentials. It does not disclose rate limiting, whether results are cached or live, what happens for non-Shopify or private stores, or how pagination beyond the limit behaves. Useful but incomplete for a tool with zero annotation coverage.

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?

Two tight sentences with the core action and payload front-loaded and no filler. The closing "Zero API key required" earns its place as a usage constraint, though the field list is dense enough to read as inventory rather than guidance.

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?

With no output schema, the description compensates by enumerating the returned fields, which is exactly what an agent needs to judge relevance. Remaining gaps are error/edge-case behavior for inaccessible stores and pagination semantics, both minor for a simple public-read tool.

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 coverage is 100%, so the baseline is 3 regardless of description content. The field enumeration (variants, prices, SKUs, stock) describes the response rather than the parameters, and the reference to /collections.json only loosely hints at collection_handle; limit and store_url semantics are left entirely to the schema.

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 names a specific verb and resource ("Fetch public Shopify store catalog feeds") and even cites the underlying endpoints (/products.json and /collections.json), so the agent knows exactly what is retrieved. The enumerated payload fields (variants, min/max prices, compare-at discounts, SKUs, stock status) remove any ambiguity, and no sibling in the catalog covers Shopify store data, so differentiation is moot.

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?

Usage is only implied: the words "public" and "Zero API key required" signal that this works for unauthenticated storefronts, which tells the agent when it is applicable. However, there is no explicit when-to-use versus alternative, no statement about which stores fail (private/password-protected shops), and no guidance on choosing between scoping by collection_handle versus fetching the whole catalog.

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