Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Get products from Walmart

get_walmart_products
Read-onlyIdempotent

Extract Walmart product data from search, category, or product links: prices, ratings, reviews, seller, and stock. Filter by price, rating, and stock to support price checks and monitoring.

Instructions

Walmart.com products from searches, category links or product links: price, was-price, rating, review count, seller, stock and sponsored flag. With details on: brand, model, UPC, specifications, description and seller rating. Filter by price, rating and stock; sort like the site. Useful for price checks, assortment research and price/stock monitoring. Runs the Apify Actor tacps126/walmart-products on your Apify account (about $0.003 per product, plus about $0.0022 per product with full details; spend per call is capped at $0.5).

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

Input Schema

NameRequiredDescriptionDefault
linksNoWalmart search, category or product links, or product item ids.
queriesNoSearch words as typed on Walmart.com, e.g. ["air fryer"].
sort_byNoOrder of search results.best_match
max_itemsNoMaximum results to return (default 50, max 1000). Cost scales with this.
max_priceNoHighest price to keep, in USD.
min_priceNoLowest price to keep, in USD.
min_ratingNoLowest star rating to keep, e.g. 4.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
in_stock_onlyNoDrop products shown as out of stock.
include_detailsNoOpen each product page for brand, UPC, specs and description (extra cost per product).
exclude_sponsoredNoDrop sponsored (ad) placements.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the description is free to add higher-value context — and it does: the underlying Actor, per-product cost, the extra charge for include_details, and a $0.5 per-call spend cap. That cost disclosure is exactly the kind of behavior an agent needs before setting max_items. It does not cover latency or partial-failure behavior when some links fail.

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?

Front-loaded with what the tool returns, then details, then filtering, then cost — a sensible priority order with no filler sentences. The dense noun-list style is appropriate for a data-extraction tool where the payload contents matter more than prose.

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 an 11-parameter tool with an output schema, the description covers inputs, filtering, cost and the details trade-off, so no critical calling information is missing. The one unresolved question is how links and queries combine — whether they are unioned or one takes precedence — which matters when an agent supplies both.

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%, so every parameter including sort_by's enum and max_items' cost note is already documented in structured form. The description's mention of filtering by price, rating and stock and sorting 'like the site' largely restates the schema rather than adding new semantics. Baseline 3 applies.

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?

The description opens with a specific verb and resource ('Walmart.com products') and immediately enumerates what comes back: price, was-price, rating, review count, seller, stock, sponsored flag, plus optional brand/UPC/specs. The resource is unmistakably Walmart retail data, which cleanly separates it from get_shopify_products and the rest of the sibling catalog.

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

Usage Guidelines4/5

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

It names three concrete use cases — price checks, assortment research, and price/stock monitoring — and states the three accepted input modes (search, category link, product link), which gives an agent clear context for when to reach for it. It stops short of explicit exclusions or pointing at an alternative tool when a different retailer's products are wanted.

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