Skip to main content
Glama

run_walmart_seller_products

Fetch products from a Walmart seller's storefront to view title, price, rating, and availability. Enter the storefront seller ID or URL to list up to 250 items.

Instructions

List products from a Walmart seller's storefront: title, price, rating, and availability. 1 point per returned record.

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": {
      "seller": "<seller>"
    },
    "name": "run_walmart_seller_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerYesWalmart storefront catalogSellerId (numeric, e.g. 102730552) or a storefront URL containing it. Not the 32-character sellerId hash from product pages and search results: that hash has no storefront page and cannot be converted. Read the id from run-walmart-product's machine.product.seller.storefront_url for any item this seller offers — items sold by Walmart itself (seller.type INTERNAL) have no storefront, so the field is null for those.
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add non-schema value by disclosing the cost model ("1 point per returned record") and the returned fields, but it omits pagination behavior, whether results are ordered/truncated, and any auth or credit-balance requirement — gaps that matter for a paginated list tool.

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

Conciseness5/5

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

Two short sentences with zero filler: the purpose/scope comes first and the cost note second. Nothing is repeated from the schema and every clause earns its place.

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?

Given a fully documented 3-parameter schema and no output schema, the definition is largely sufficient — the agent knows what it returns, what it costs, and where to get the required ID. The remaining shortfall is the absence of pagination/usage guidance, which an agent must infer from `start_page` and `max_items`.

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% and the `seller` description is unusually thorough (catalogSellerId vs. the 32-char sellerId hash, where to read the ID, and the INTERNAL null case), so the baseline of 3 applies. The tool description itself adds no parameter-level detail beyond the schema, though it does clarify the shape of records returned.

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 ("List products from a Walmart seller's storefront") and enumerates the returned fields (title, price, rating, availability). This scoping is clearly distinct from run_walmart_product (single item), run_walmart_product_search (keyword search), and run_walmart_seller (seller profile), so an agent can select it without opening the schema.

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 main description gives no when-to-use or when-not-to-use guidance relative to the sibling Walmart tools. The real routing signal lives in the `seller` parameter description (use catalogSellerId from run-walmart-product's machine.product.seller.storefront_url, and note that INTERNAL/Walmart-sold items have no storefront), which is useful but is parameter-level rather than tool-level guidance.

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