Skip to main content
Glama

Scrape Walmart product search

walmart_search
Read-only

Searches Walmart for query and returns the products as JSON: name, price and wasPrice, rating, reviewCount, brand, seller, availability, image, a product url, sponsored, unitPrice, priceRange, promotions, fulfillment, deliveryAvailable and variants. The response also carries the search's totalResults, pages, filters and sponsoredProducts. Sort with sort, filter with min_price/max_price, and collect up to max_results across pages. Returns JSON. Billed like an API request; listing plugins bill one unit per result page they fetch, so keep max_results modest.

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": {
      "query": "<query>"
    },
    "name": "walmart_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page to start from (~40 per page). Default: 1.
sortNoOrdering: best_match, price_low, price_high, best_seller, rating_high, new. Default: best_match.
queryYesWhat to search, e.g. 'laptop' or 'coffee maker'.
max_priceNoHighest price to include (USD).
min_priceNoLowest price to include (USD).
max_resultsNoHow many products to collect across pages. Default: 40.
proxy_countryNoProxy country the request is sent from (ISO-2, e.g. 'US', 'DE'). Defaults to US.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / max_price / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / max_price / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / max_results / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / max_results / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / min_price / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / min_price / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / minimum
      Added value: +-9007199254740991
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the added value here is the billing model: 'Billed like an API request; listing plugins bill one unit per result page they fetch.' That is genuine cost/behavior context an agent cannot get from annotations or schema, and it motivates the max_results constraint. It stops short of noting rate limits, blocking/anti-bot behavior, or empty-result handling.

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?

Purpose and return shape are front-loaded, and the cost warning is positioned where it matters. The field enumeration is long but earns its place since no output schema exists; a slightly tighter split into separate sentences for return shape vs. controls would read better.

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?

With no output schema, the description correctly compensates by naming every returned field plus the response envelope (totalResults, pages, filters, sponsoredProducts), and it discloses the billing implications. The remaining gap is geo behavior via `proxy_country` and what happens when requested results exceed available pages.

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 coverage is 100%, so all seven parameters are already documented, and the description mainly restates sort/price filters/max_results. It does clarify that max_results aggregates 'across pages,' but omits any mention of `page` and `proxy_country`, which materially change results (geo-localized pricing/availability).

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 ('Searches Walmart for `query`') and immediately enumerates the returned product fields, so an agent can tell this apart from amazon_search, ebay_search, or google_shopping without opening any 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?

Gives operational guidance inside the tool — sort with `sort`, filter with `min_price`/`max_price`, cap with `max_results` — and a cost-driven reason to keep results modest. It never says when to prefer this over the sibling marketplace/aggregator search tools, so selection guidance is implied rather than stated.

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