Skip to main content
Glama

discover_ecommerce_store_leads

Read-onlyIdempotent

Find verified B2B ecommerce store leads by niche, country, platform, or installed tech, or enrich domain lists with emails, phones, addresses, apps, Shopify Plus status, and estimated SaaS spend.

Instructions

Discover verified B2B ecommerce leads across 16,345+ indexed storefronts (10,148 Shopify + 6,197 custom-domain WooCommerce) plus live web niche search, or enrich a list of domains with contact emails, phones, postal addresses, 65+ installed apps, Shopify OS 2.0 Web Pixels, Shopify Plus status, and monthly SaaS spend.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discover_ecommerce_store_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsNoOptional list of store domains to enrich directly. Leave empty to discover stores by niche/tech criteria.
maxResultsNoMaximum number of store leads to return (1-200).
missingTechNoApp or pixel that must NOT be installed (ideal for agency pitch lists, e.g. 'TikTok Pixel').
searchQueryNoNiche or product keyword (e.g. 'coffee', 'skincare', 'pickleball').
requiredTechNoApp or pixel that must be installed (e.g. 'Klaviyo', 'Meta Pixel').
countryFilterNoTwo-letter ISO country code (e.g. 'US', 'GB', 'AU', 'CA', 'DE').
onlyWithEmailNoReturn only stores with at least one verified contact email.
platformFilterNoFilter by ecommerce platform.any
minTechSpendUsdNoMinimum estimated monthly software spend in USD (e.g. 100).
onlyShopifyPlusNoReturn only verified Shopify Plus storefronts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/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 still adds meaningful behavioral context the annotations cannot: the size and composition of the indexed corpus, the presence of a live web search mode, and the specific enrichment payload (emails, phones, postal addresses, apps, pixels, Shopify Plus status, SaaS spend). Missing are rate limits, credit costs, or data freshness caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

There is no filler, but the whole definition is a single ~55-word sentence with nested parentheticals that merges three distinct modes without any structural separation. Front-loading the discovery mode is good; the run-on construction makes it harder to scan than two or three short sentences would.

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 must carry the return-value burden, and it does so by enumerating the enrichment fields an agent can expect. All ten parameters are covered by the schema and the tool has no required inputs, so an agent has enough to call it correctly; only the mode-selection rule is left implicit.

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 every one of the ten parameters is already documented in the schema, making 3 the baseline. The description reinforces the tech-stack and SaaS-spend concepts (65+ apps, OS 2.0 Web Pixels, Shopify Plus) that map to requiredTech, missingTech, minTechSpendUsd and onlyShopifyPlus, but adds no syntax, format, or interaction detail beyond that.

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 ('Discover verified B2B ecommerce leads') and quantifies the indexed corpus (10,148 Shopify + 6,197 WooCommerce), then states a second mode ('enrich a list of domains'). It is distinguishable from the siblings (app reviews, ATS jobs), but packing discovery, live web search, and enrichment into one clause blurs which capability is primary.

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?

The 'or enrich a list of domains' phrasing plus the schema note on 'domains' implies the two modes, but the description never states the selection rule outright, nor any when-not conditions or prerequisites. The agent has to infer from the parameter description rather than from the tool description itself.

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