Skip to main content
Glama

Walmart seller

run_walmart_seller
Read-onlyIdempotent

Get a Walmart marketplace seller profile by seller ID: rating, location, and contact info. Flat 5 points per successful run.

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / seller / description
      Previous value: -"Seller catalog ID or storefront URL. e.g. 101638471"New value: +"Walmart 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."
  2. Changed1 schema field changed
    • changedInput schema / properties / seller / description
      Previous value: -"Walmart storefront catalogSellerId (numeric, e.g. 101638471) or storefront URL (https://www.walmart.com/seller/101638471). Not the 32-character sellerId hash from product pages — get the storefront URL from run_walmart_product's machine.product.seller.storefront_url."New value: +"Seller catalog ID or storefront URL. e.g. 101638471"
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: a flat cost of 5 points per successful run, plus the shape of the returned profile (rating, location, contact info) in the absence of an output schema.

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 compact sentences, zero filler, with the purpose and output fields front-loaded before the cost note. Nothing could be trimmed without losing information.

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 tool with no output schema, the description supplies the return fields and the per-call cost, and the schema handles the tricky ID format. The main omission is routing guidance relative to run_walmart_product / run_walmart_seller_products, which leaves the agent to infer the workflow.

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 schema's own text is unusually thorough, explaining catalogSellerId vs. the unusable 32-character hash and how to derive the ID from storefront_url. The description adds nothing beyond the schema, so the baseline 3 applies.

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 and resource ('Get a Walmart marketplace seller profile by seller ID') and even names the returned fields (rating, location, contact info). It is clearly distinct from run_walmart_product and run_walmart_seller_products, though it never names a sibling to sharpen the contrast.

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?

There is no when-to-use or when-not-to-use guidance and no alternatives named. The agent must infer from the sibling list whether seller lookup, seller products, or product lookup is the right entry point, and nothing addresses what to do when only a 32-character hash is available (that nuance lives only in the schema).

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