Skip to main content
Glama

StoreTechScan — Ecommerce Tech Stack & ICP

Inspect Ecommerce & Company Domains

inspect_domains

Live 4-stage enrichment for 1–25 unique domains per call: detects ecommerce platforms & marketing/support/pixel stack (Shopify, WooCommerce, Klaviyo, Gorgias, Recharge, Meta/TikTok Pixel, GA4), samples public Shopify /products.json catalog counts & native-currency min/median/max prices, scores 1.0–5.0 ICP prospect fit + active-merchant check + wholesale/B2B signal, and extracts public same-domain role emails (hello@, sales@) & social URLs. Pass multiple domains together in one array rather than calling 1 domain at a time. Paid mode (via HTTP header Authorization: Bearer zsk_live_... or X-API-Key) debits 1 credit per reachable billable domain ($0 for DNS/TLS/timeout/5xx/429/WAF failures), enables calibrated AI ICP scoring, and returns a durable job_id recoverable via get_inspection_results.

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": {
      "domains": "<domains>"
    },
    "name": "inspect_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYes
platformNoOptional filter: match primary platform or detected tech (e.g. "Shopify", "WooCommerce", "Klaviyo").
min_fit_scoreNoOptional filter: minimum 1.0–5.0 ICP prospect fit score (e.g. 3.5 or 4.0).
b2b_wholesale_onlyNoOptional filter: return only domains with detected B2B, trade, or wholesale signals.
real_merchant_onlyNoOptional filter: return only verified active merchants/operators (excludes parked/empty stores).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say openWorldHint=true, readOnlyHint=false, idempotentHint=false, destructiveHint=false; the description goes well beyond that by disclosing the credit model (1 credit per reachable billable domain, $0 for DNS/TLS/timeout/5xx/429/WAF failures), the auth header formats, and the fact that AI ICP scoring is gated to paid mode. That cost and failure-billing detail is exactly the behavioral context an agent needs before invoking a metered 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?

Front-loaded with the core capability and the batch limit, then layered with pricing and recovery details, so nothing important is buried. It is a single very dense sentence with stacked parenthetical tech lists that is harder to scan than a short structured breakdown would be, but every clause carries operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by naming what comes back: detected platforms/pixels, sampled catalog counts and native-currency price stats, fit scores, emails and social URLs, plus a durable job_id. Combined with the credit and auth disclosure, an agent has enough to call this correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 80% schema coverage the baseline is 3, but the description adds meaning by explaining what the filters operate on: the fit score is a 1.0–5.0 ICP score, the merchant filter reflects an active-merchant check that excludes parked/empty stores, and the wholesale filter keys off detected B2B/trade signals. It does not explicitly map those to the platform or min_fit_score parameter names, leaving the correspondence inferential.

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?

States a specific verb and resource ('Live 4-stage enrichment for 1–25 unique domains per call') and then enumerates the four stages concretely: tech-stack detection, Shopify catalog/price sampling, 1.0–5.0 ICP fit scoring, and role-email/social extraction. It also distinguishes itself from the sibling get_inspection_results by positioning that tool as the job-retrieval path rather than a competing inspection call.

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 explicit batching guidance ('Pass multiple domains together in one array rather than calling 1 domain at a time') and explains the paid-mode path plus how to recover durable results via get_inspection_results. It stops short of stating when this tool is the wrong choice versus get_ecommerce_benchmark_2026, so there is no true when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources