Skip to main content
Glama
Sign In
CommerceWeave MCP

CommerceWeave MCP

by mysterekkk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List products across stores

commerce_list_products
Read-onlyIdempotent

Lists products and offers from connected commerce platforms in a normalized shape, including SKUs, EANs, prices, stock, and variants, with paging and name filtering for catalog lookup.

Instructions

Lists products/offers in a normalized shape (source ids, SKU, EAN, gross prices, stock, variants). Pages are per connection: one connection per call is recommended for large catalogs. Stock total is null when the platform does not manage a quantity. Base prices carry no currency (null).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryNoName substring filter.
connectionIdsNoConnection ids to include (see commerce_list_connections). Omit for all connections.
includeVariantsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered structurally. The description adds genuine behavioral detail beyond that: the per-connection pagination model and the null semantics for stock total and base prices, which prevent misreading results as zero/empty. It still does not discuss rate limits, truncation, or failure modes.

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?

Dense but front-loaded: the payload shape leads, then pagination constraints, then null-edge-cases. No filler sentences; each sentence carries distinct information, though the field-list parenthetical is packed tightly enough to be slightly hard to scan.

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?

No output schema exists, so the description must describe returns, and it does so at field-group level plus two null sentinels that would otherwise cause wrong conclusions. For a read-only list tool with five optional parameters, this is close to sufficient; the main gap is that it never says what a product object's identity key is or how variants relate to parent products.

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?

With schema coverage at 40%, the description must carry weight, and it does for the critical ambiguity: "pages are per connection" explains that page/limit apply per connection rather than globally, and the null-price note clarifies price fields. However, query, limit bounds, and connectionIds behavior are left entirely to the schema, so the compensation is partial.

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 concrete verb and resource ("Lists products/offers") and enumerates the normalized fields returned (source ids, SKU, EAN, gross prices, stock, variants), which tells an agent what kind of payload to expect. It does not explicitly distinguish itself from search-style siblings like commerce_find_product, so it stops short of a 5.

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?

Provides one actionable operational guideline: pages are per connection and one connection per call is recommended for large catalogs. It does not state when to prefer this over commerce_find_product or commerce_low_stock, nor any exclusions, so usage is implied rather than spelled out.

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