Skip to main content
Glama

Walmart product search

run_walmart_product_search
Read-onlyIdempotent

Search Walmart products by keyword: title, price, rating, and seller. 1 point per returned record.

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": {
      "keyword": "<keyword>"
    },
    "name": "run_walmart_product_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Options: price_low = Price: low to high, price_high = Price: high to low, best_seller = Best seller, new = New arrivals, rating_high = Highest rated
keywordYesSearch term. e.g. wireless mouse
max_itemsNoMax items (up to 250) Default: 25.
max_priceNoMax price
min_priceNoMin price
start_pageNoStarting page Default: 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Search term, e.g. 'wireless mouse'."New value: +"Search term. e.g. wireless mouse"
    • changedInput schema / properties / max_items / description
      Previous value: -"Maximum number of products to return (1-250, default 25). Billed at 1 point per returned record."New value: +"Max items (up to 250) Default: 25."
    • changedInput schema / properties / max_price / description
      Previous value: -"Maximum price, in USD."New value: +"Max price"
    • removedInput schema / properties / max_price / minimum
      Removed value: -0
    • changedInput schema / properties / min_price / description
      Previous value: -"Minimum price, in USD."New value: +"Min price"
    • removedInput schema / properties / min_price / minimum
      Removed value: -0
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order (default best_match)."New value: +"Sort by. Options: price_low = Price: low to high, price_high = Price: high to low, best_seller = Best seller, new = New arrivals, rating_high = Highest rated"
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "best_match",
      -  "price_low",
      -  "price_high",
      -  "best_seller",
      -  "new",
      -  "rating_high"
      -]New value: +[
      +  "price_low",
      +  "price_high",
      +  "best_seller",
      +  "new",
      +  "rating_high"
      +]
    • changedInput schema / properties / start_page / description
      Previous value: -"Result page to start from (default 1)."New value: +"Starting page Default: 1."
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact beyond annotations: "1 point per returned record," a cost/consumption disclosure. However it omits pagination behavior despite the start_page parameter, so the addition is partial.

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 sentence plus a short cost clause, front-loaded with the action and resource. No filler, though the cost note reads as an appended fragment rather than integrated structure.

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 read-only search tool with full schema coverage and clear annotations, the description supplies the essentials: what it searches, what it returns, and the per-record cost. Pagination semantics for start_page are the only notable omission, and no output schema exists to fill the return-value gap.

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%, including the sort enum and price-range bounds, so the schema carries the parameter burden. The description's list of fields (title, price, rating, seller) describes return data rather than adding meaning to parameters, 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 ("Search Walmart products by keyword") and enumerates the fields it returns (title, price, rating, seller), so an agent can distinguish it from run_walmart_product (single-item lookup) or run_walmart_seller_products. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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?

The description implies a keyword-search use case but gives no when-to-use, when-not-to-use, or alternative guidance. With run_walmart_product and run_walmart_seller_products in the same family, the agent gets no help deciding between search vs. detail vs. seller-scoped retrieval.

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