Skip to main content
Glama
sec-edgar-fda-b2b-mcp

sec-edgar-fda-b2b-mcp

get_shopify_store_catalog

Read-onlyIdempotent

Extract live product catalogs, prices, discounts, and availability from Shopify stores to monitor competitor pricing and research SKUs. Returns up to 25 products per store with URLs and stock status.

Instructions

Extract live product catalogs, prices, discounts, and availability from Shopify stores.

Use this tool for e-commerce competitor price monitoring and SKU research.
Returns a JSON array of up to 25 products containing storeDomain, title, vendor, price,
compareAtPrice, available, and productUrl. Requires the APIFY_TOKEN environment variable.

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_domains": "<store_domains>"
    },
    "name": "get_shopify_store_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
store_domainsYesList of Shopify store domains without protocol (e.g., ['allbirds.com', 'gymshark.com']).
max_products_per_storeNoMaximum number of products to extract per Shopify store (1-200).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / max_products_per_store / description
      Added value: +"Maximum number of products to extract per Shopify store (1-200)."
    • addedInput schema / properties / max_products_per_store / maximum
      Added value: +200
    • addedInput schema / properties / max_products_per_store / minimum
      Added value: +1
    • addedInput schema / properties / store_domains / description
      Added value: +"List of Shopify store domains without protocol (e.g., ['allbirds.com', 'gymshark.com'])."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description only needs to add context — and it does: it discloses the APIFY_TOKEN environment variable prerequisite and describes the return shape. It omits rate limits, pagination, and failure behavior when a domain is not a Shopify store, which is meaningful for a scraping tool.

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?

Three short, front-loaded blocks: purpose, usage, then returns and prerequisites. No filler sentences, though the returns paragraph partially duplicates the existing output schema.

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?

For a two-parameter read tool with full schema coverage, annotations, and an output schema, the description covers purpose, when-to-use, and the auth prerequisite. The remaining gap is operational behavior — what happens for non-Shopify domains and how batching across multiple store_domains behaves.

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%, so both parameters are already documented with examples and bounds. The description adds only a soft hint on volume ('up to 25 products'), which in fact conflicts with the schema's maximum of 200 and reads as if 25 were a hard cap rather than the default. Baseline 3 applies.

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?

Names a specific verb ('Extract') and resource ('live product catalogs, prices, discounts, and availability from Shopify stores'), plus enumerates the returned fields. This is far more precise than a tautology, though it never explicitly contrasts itself with the marketplace siblings (which serve unrelated domains, so ambiguity risk is low).

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

Usage Guidelines4/5

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

Gives an explicit use case: 'Use this tool for e-commerce competitor price monitoring and SKU research.' That establishes clear context, but there is no when-not-to-use guidance and no named alternative for adjacent needs such as general web enrichment.

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