Skip to main content
Glama

FoxAPIs data sources

Shopify store

shopify_store
Read-onlyIdempotent

A Shopify store from its domain: product count, price range and average, vendors and product types, from its storefront. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "domain": "<domain>"
    },
    "name": "shopify_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesFor example: "allbirds.com"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, so the safety profile is known. On top of that the description adds genuinely non-structured facts: 2 credits per call, no charge for an empty answer, and a required FoxAPIs key. It stops short of saying whether a non-Shopify domain returns empty data or an error, which matters for an open-world lookup.

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?

One compact sentence front-loads the resource and enumerates the returned metrics, followed by two short clauses on cost and auth. Nothing is redundant, though the colon-list of metrics makes the first sentence dense and the metrics could be read faster as a list.

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 single-parameter read-only lookup with no output schema and full schema coverage, the description supplies the essential business facts (cost, no-charge-on-empty, key requirement) and the metric list. The remaining gap — behavior on non-Shopify domains and whether results are cached/live — is minor but real for an open-world tool.

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 coverage is 100% and the single `domain` property already carries an example ("allbirds.com"). The description's 'from its domain' confirms the input is a bare hostname rather than a URL with scheme or path, but adds no further syntax constraints. Baseline 3 applies when the schema does the heavy lifting.

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 the resource (a Shopify store) and the exact payload returned: product count, price range and average, vendors, product types. That is specific enough for an agent to distinguish it from platform-sibling tools like appstore_app or steam_game, though it never explicitly says so. It slightly obscures the verb by framing the tool as a noun phrase rather than 'get store metrics for a domain'.

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 implied by 'from its storefront' — the domain must be a Shopify storefront — but the description never states when to pick this over another store/entity lookup, nor what happens for a non-Shopify domain. The cost and key requirements are helpful context, but cost is pricing, not usage 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