Skip to main content
Glama

Walmart search results

get_walmart_search_results
Read-only

Scrape Walmart search results using ScrapingBee.

Scope: one query per call. To run many queries in one pass, or to write results to disk instead of into the conversation, use the ScrapingBee CLI — scrapingbee <command> --input-file queries.txt --output-dir results.

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

Input Schema

NameRequiredDescriptionDefault
tagNoResponse-header label only.
queryYesThe search query to perform.
deviceNoThe device to use for the search (desktop, mobile, tablet).desktop
domainNoThe domain to use for the search (Example: com, ca, com.mx, etc.) for localization.
sort_byNoThe sort order to use for the search (best_match, price_low, price_high, best_seller).best_match
add_htmlNoWhether to return the HTML along with the search results.
store_idNoSpecific Walmart store ID for localization.
max_priceNoThe maximum price to use for the search.
min_priceNoThe minimum price to use for the search.
screenshotNoForce a browser screenshot (returns base64 image).
start_pageNoThe page number to return (default 1).
delivery_zipNoThe zip code to use for delivery localization.
light_requestNoWhether to use a light request or not.
fulfillment_typeNoThe fulfillment type to use for the search (in_store).
fulfillment_speedNoThe fulfillment speed to use for the search (today, tomorrow, 2_days, anytime).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds that results land in the conversation rather than on disk and that each call handles a single query, which is genuinely useful behavioral context. It says nothing about credit consumption, rate limits, or latency, which are material for a paid scraping endpoint.

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?

Two short sentences, front-loaded with the core action, followed by the batching constraint. No filler and nothing repeated from the schema.

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 15-parameter tool with a full output schema and readOnly annotations, the description covers the essentials: what it does, call scope, and an escalation path for bulk work. The only gap is the absence of any note on cost/credits or how to interpret the returned result set.

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% across all 15 parameters, so the schema carries full documentation burden and the baseline applies. The description adds no meaning beyond the schema — no guidance on localization fields (domain, store_id, delivery_zip) or on the interaction between light_request, add_html, and screenshot.

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 ('Scrape Walmart search results') plus the underlying provider (ScrapingBee), which implicitly separates it from the Amazon/Google/YouTube siblings. It does not explicitly distinguish itself from get_walmart_product_details or fast_search, so it falls short of a 5.

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?

Gives a concrete exclusion: one query per call, and steer toward the ScrapingBee CLI for bulk queries or writing results to disk. That is real when-to-use/when-not guidance, but no guidance is offered relative to sibling MCP tools such as fast_search or get_walmart_product_details.

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