Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Analyze Shopify stores (location, catalog, contacts)

analyze_shopify_stores
Read-onlyIdempotent

Retrieve catalog, pricing, activity, and contact details for Shopify stores, then filter and sort results by size, price, or recency.

Instructions

For each Shopify store: name, city and country, currency, product and collection counts, a catalog snapshot (price range and median, share on sale and in stock, top brands and product types, newest product) and its e-mails, phones and social profiles. Filter by size, price, activity and e-mail; sort by size or newest product. Non-Shopify sites are skipped for free. Runs the Apify Actor tacps126/shopify-store-analyzer on your Apify account (about $0.004 per store; spend per call is capped at $0.5).

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": "analyze_shopify_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
storesYesStore websites or domains, e.g. ["allbirds.com", "gymshark.com"].
sort_byNoOrder the stores before the limit applies.default
countriesNoKeep only stores based in these countries (ISO codes or names).
max_itemsNoMaximum results to return (default 20, max 1000). Cost scales with this.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
max_productsNoOnly stores with at most this many products (small stores).
min_productsNoOnly stores with at least this many products.
require_emailNoOnly stores where an e-mail address was found.
include_contactsNoAlso read the store's contact pages for e-mails, phones and socials.
active_within_daysNoOnly stores that published a product in the last N days.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.17.0
    • addedInput schema / properties / active_within_days
      Added value: +{
      +  "description": "Only stores that published a product in the last N days.",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / max_products
      Added value: +{
      +  "description": "Only stores with at most this many products (small stores).",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / min_products
      Added value: +{
      +  "description": "Only stores with at least this many products.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / require_email
      Added value: +{
      +  "default": false,
      +  "description": "Only stores where an e-mail address was found.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / sort_by
      Added value: +{
      +  "default": "default",
      +  "description": "Order the stores before the limit applies.",
      +  "enum": [
      +    "default",
      +    "most_products",
      +    "fewest_products",
      +    "highest_price",
      +    "lowest_price",
      +    "newest_product",
      +    "name"
      +  ],
      +  "type": "string"
      +}
  2. Addedv0.10.1

TDQS

A3.7/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, openWorld, non-destructive), and the description adds genuinely new behavior: it runs the Apify Actor tacps126/shopify-store-analyzer on the caller's Apify account, costs about $0.004 per store, and spend per call is capped at $0.5. The free-skip of non-Shopify domains is a useful behavioral disclosure. Missing only operational details such as latency or failure modes, so it stops short of a 5.

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 sentences, front-loaded with the output payload, then filtering/sorting, then cost and platform behavior. The first sentence is a dense run-on list of return fields that would scan better as a short list, but no sentence is wasted and none is redundant.

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 10-parameter tool with a nested object and a published output schema, the description covers cost, platform dependency and the free non-Shopify skip, which are the things an agent could not learn from the schema. It arguably over-invests in restating return fields that the output schema already defines, while under-explaining how extra_input merging 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 the schema already explains stores, countries, max_items, min/max_products, require_email, include_contacts, active_within_days, sort_by and extra_input. The description only loosely groups these into 'size, price, activity and e-mail' filters and never mentions the cost-linkage of max_items, so it adds little beyond the structured fields.

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 names a specific verb and resource (analyze Shopify stores) and enumerates exactly what is returned: location, currency, product/collection counts, catalog snapshot, and contact details. The purpose is unmistakable, but it never contrasts itself with the sibling get_shopify_products, leaving the agent to infer the division of labor.

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?

It gives in-tool usage cues ('Filter by size, price, activity and e-mail; sort by size or newest product') which map directly to the schema parameters. However, there is no when-to-use/when-not guidance versus alternatives, and the only exclusion mentioned is 'Non-Shopify sites are skipped', which is a behavior rather than a selection rule.

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