Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

extract_shopify_store_catalog

Read-onlyIdempotent

Extract e-commerce product catalogs from Shopify stores, including SKU variants, pricing, discounts, stock status, vendor tags, and images. Filter by collection or limit products per store.

Instructions

Extract complete e-commerce product catalogs, SKU variant pricing, compare-at discount percentages, inventory stock status, vendor tags, and image URLs from any Shopify-powered store.

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": {
      "stores": "<stores>"
    },
    "name": "extract_shopify_store_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
storesYesShopify store domains or URLs to scrape (e.g., ["allbirds.com", "gymshark.com"]).
collectionHandleNoOptional Shopify collection slug filter (leave empty for all store products).
maxProductsPerStoreNoMaximum number of products to extract per Shopify domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that the operation scrapes live storefronts (implying network dependence and possible bot-blocking) and lists what data comes back. However, it says nothing about rate limits, failure/partial-result behavior across the up-to-20 stores, or what happens when a store or collection is invalid.

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?

A single sentence with the action verb front-loaded and the payload contents listed compactly. Every clause carries information about what is extracted; the list is dense but not padded. It could be tightened slightly, but there is no wasted prose.

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 only three fully documented parameters and no output schema, the description's enumeration of returned fields compensates well and tells an agent what to expect. The remaining gap is operational detail — behavior across multiple stores, invalid domains, or partial failures — which matters given the up-to-20-store array but is not addressed.

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%, with clear docs for stores, collectionHandle and maxProductsPerStore, so the baseline is 3. The description adds no further meaning to the parameters — it does not clarify that collectionHandle acts as a filter or that maxProductsPerStore caps results per domain, though the schema already states both.

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?

The description opens with a specific verb+resource ("Extract complete e-commerce product catalogs") and then enumerates the concrete data fields returned (variant pricing, compare-at discount percentages, stock status, vendor tags, image URLs). An agent immediately knows this is a Shopify storefront scraping tool. It does not differentiate from siblings, but the sibling list contains no overlapping e-commerce tools, so the gap is minor.

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: "from any Shopify-powered store" signals the domain and the schema's collectionHandle/maxProductsPerStore hints at filtering and volume control. There is no explicit statement of when to use this versus another approach, no prerequisites (e.g., store must be publicly accessible), and no exclusions such as password-protected or non-Shopify sites.

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