Walmart Remote MCP Server

walmart_product: GET /

hasdata_walmart_product_getWalmartProduct

Read-only

Get Walmart Product Details

Scrapes one Walmart product page on a chosen storefront by item id or URL. Returns title, brand, model, UPC, condition, availability, price with strikethrough before-price and unit price, the seller holding the buy box with its rating and return policy, badges, SNAP EBT eligibility, Walmart+ savings, star rating with the per-star review breakdown and AI review summaries, images, category path, highlights, specifications, AI-generated key item features, variant axes with every option and the itemId each combination resolves to, fulfillment details, and the other-sellers block: when otherOffers is enabled, the full offer list with each seller name, storefront URL, price, condition, shipping cost, delivery date and return policy plus its count; when disabled, only the competitor count and cheapest competing price the page itself advertises, which is often absent (notably on walmart.ca). Use for price and buy-box monitoring, seller and marketplace competitor tracking, assortment enrichment of item ids harvested from search, and variant mapping.

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

Input Schema

Name	Required	Description
`url`	No	A full Walmart product URL to scrape as is. When provided, it overrides `itemId` and the storefront is taken from the URL itself. Required unless `itemId` is provided.
`domain`	No	Walmart storefront the item belongs to. Each storefront has its own catalog, item ids, prices and currency, so an id from one storefront does not resolve on another. Ignored when `url` is provided. Default is `walmart.com`.
`itemId`	No	Walmart item id, taken from a product URL or from the id field of the Walmart Search API response. On `walmart.com` it is numeric (for example `14977205582`), on `walmart.ca` an alphanumeric code (for example `6NZMJ5CW6MH2`). Required unless `url` is provided.
`language`	No	Language of the product details. Availability depends on the storefront - `walmart.com` serves `en` and `es`, `walmart.ca` serves `en` and `fr`. A language the storefront does not support falls back to its default.
`otherOffers`	No	Also collect the offers of other sellers competing for this item - each seller name, storefront, price, condition, shipping cost, delivery date and return policy. This takes an extra request to Walmart and costs 5 credits on top of the base 10, whether or not the item turns out to have competing sellers. Enable it to get the seller list - it is the only reliable way to know whether other sellers exist, because the product page's own advertised competitor count is often absent (notably on `walmart.ca`) even when sellers are available. With the switch off, the `otherOffers` block is returned only when the page itself advertises a count, and then carries just that count and the cheapest competing price without the seller list. Default is `false`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / otherOffers / description

Previous value: -"Also collect the offers of other sellers competing for this item - each seller name, storefront, price, condition, shipping cost, delivery date and return policy. This takes an extra request to Walmart and costs 5 credits on top of the base 10, whether or not the item turns out to have competing sellers. How many competitors the item advertises, and the cheapest competing price, are returned in the `otherOffers` block whether the switch is on or off, so it can be left off until the count shows there is something to collect. Default is `false`."New value: +"Also collect the offers of other sellers competing for this item - each seller name, storefront, price, condition, shipping cost, delivery date and return policy. This takes an extra request to Walmart and costs 5 credits on top of the base 10, whether or not the item turns out to have competing sellers. Enable it to get the seller list - it is the only reliable way to know whether other sellers exist, because the product page's own advertised competitor count is often absent (notably on `walmart.ca`) even when sellers are available. With the switch off, the `otherOffers` block is returned only when the page itself advertises a count, and then carries just that count and the cheapest competing price without the seller list. Default is `false`."

First observedSep 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so the safety profile is covered; the description adds cost and side-effect detail the annotations cannot, namely base 10 credits plus 5 for otherOffers 'whether or not the item turns out to have competing sellers' and that enabling it 'takes an extra request to Walmart'. It also discloses degraded-output conditions when otherOffers is off, including that the count is 'often absent (notably on walmart.ca)'. Missing only return-shape/pagination mechanics, which is minor for a scrape.

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?

Front-loaded with the purpose, and the long return-field enumeration is dense but each item is a distinct data point an agent may need to decide fitness for a task. The single mega-sentence enumerating every returned field is heavy and could be broken into bullets or trimmed, which is the only thing keeping it from a 5.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing returns, and it does so exhaustively including the conditional otherOffers block, the per-star review breakdown and AI review summaries. Combined with credit cost, storefront/id coupling and failure modes on walmart.ca, an agent has everything needed to call this correctly and budget for it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents enums and defaults, so the baseline is 3; the description still adds meaning by tying storefront to identity ('an id from one storefront does not resolve on another'), noting per-storefront id formats and language fallback, and framing otherOffers in terms of cost and reliability rather than mere type. It does not restate syntax but does explain consequences, which is genuine added value over the schema.

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 ('Scrapes one Walmart product page on a chosen storefront by item id or URL') and immediately enumerates what comes back, so the agent knows exactly what the call produces. The closing use-case list ('price and buy-box monitoring, seller and marketplace competitor tracking, assortment enrichment of item ids harvested from search, variant mapping') implicitly separates it from the sibling search and reviews tools.

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

Usage Guidelines5/5

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

Gives explicit situational guidance ('Use for price and buy-box monitoring, seller and marketplace competitor tracking, assortment enrichment of item ids harvested from search, and variant mapping') and names the condition that changes behavior: enable otherOffers to get the seller list, leave it off for the page-advertised count only. It even explains why the switch matters ('the only reliable way to know whether other sellers exist'), which is decision-grade guidance, not just context.

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

All Walmart Remote MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.