Skip to main content
Glama

Search Walmart

search_walmart
Read-onlyIdempotent

Searches walmart.com (US) by keyword and returns up to 20 products from the first results page (title, url, price, rating, reviews_count, availability, seller). It does not search other Walmart countries and does not return reviews or price history; for prices at other stores use google_shopping_prices. Required: query.

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

Input Schema

NameRequiredDescriptionDefault
queryYesProduct search text, 1-500 characters, e.g. "coffee maker".
resultsNoMaximum products returned, integer 1-20, default 10, e.g. 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Product search query."New value: +"Product search text, 1-500 characters, e.g. \"coffee maker\"."
    • changedInput schema / properties / results / description
      Previous value: -"Maximum number of Walmart products to return."New value: +"Maximum products returned, integer 1-20, default 10, e.g. 5."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds real behavior beyond the annotations: US-only scope, first-results-page cap, and an explicit list of returned fields. It doesn't mention rate limits, bot-blocking/anti-scraping behavior, or failure modes, which would matter for an openWorldHint scraping tool, but the annotation set already covers safety and idempotency.

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?

One tight paragraph with the purpose and scope front-loaded, followed by exclusions and the alternative. The trailing "Required: query" is the one sentence that doesn't earn its place since the schema marks it required.

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?

No output schema exists, and the description compensates by listing the exact returned fields and the 20-item cap. Combined with the explicit scope and exclusions, an agent has everything needed to select and call it correctly.

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 both parameters are already fully documented with types, bounds, defaults, and examples. The description's only addition is "up to 20 products," which merely restates the schema maximum, and "Required: query" is redundant. Baseline 3 is correct when the schema does the work.

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.com (US) by keyword") and enumerates what is returned (title, url, price, rating, reviews_count, availability, seller). Scope limits are stated up front, letting an agent distinguish it from google_shopping_prices 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 Guidelines5/5

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

Explicitly names the exclusions (no other Walmart countries, no reviews, no price history) and routes to the alternative for prices at other stores (google_shopping_prices). It also states the fixed page depth ("first results page"), so the agent knows there is no pagination.

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