Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_ecom_shopify_feed_extractor

Extract a Shopify store's public products.json catalog and return product pricing with stock summaries for e-commerce research and inventory checks.

Instructions

[E-Commerce Intelligence] Extract the public Shopify products.json catalog with pricing and stock summary Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://ecom.caelaralabs.com.

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": {
      "url": "<url>"
    },
    "name": "caelara_ecom_shopify_feed_extractor"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesShopify store URL
pageNoPage number (default 1)
limitNoProducts per page 1-250 (default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does contribute real context — the upstream endpoint called and measured latency figures (p50 11 ms, p95 15 ms) — but says nothing about failure behavior on non-Shopify or blocked stores, rate limits, or pagination termination, which matter for an unannotated network fetch 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?

Two sentences, front-loaded with the category tag and the core capability, so the essential information is read first. The benchmark parenthetical and endpoint disclosure are secondary but short and plausibly useful for trust in an unannotated tool.

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

Completeness3/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 is the only place a caller learns what comes back, and 'pricing and stock summary' is only a sketch of the returned shape. Combined with no annotations, the definition leaves the mutation/safety and response-shape story thin, though the 100%-covered input schema reduces the burden.

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 all three parameters (url, page, limit) are already documented in the schema, establishing the baseline of 3. The description adds no clarification beyond that, such as whether 'url' expects a bare domain or a full scheme/path.

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?

States a specific verb ('Extract') and resource ('public Shopify products.json catalog') and scopes the payload to 'pricing and stock summary'. An agent can tell it fetches a raw catalog feed rather than parsing JSON-LD or computing composites, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

The word 'public' implies the store must expose products.json, but there is no explicit when-to-use guidance, no preconditions, and no routing to alternatives such as the JSON-LD parser or the product intel composite tools. The agent must infer selection from the name and tag alone.

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

Deploy Server

Other Tools