Skip to main content
Glama

Walmart product details

get_walmart_product_details
Read-only

Scrape Walmart product details 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": {
      "product_id": "<product_id>"
    },
    "name": "get_walmart_product_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoResponse-header label only.
deviceNoThe device to use for the request (desktop, mobile, tablet).desktop
domainNoThe domain to use for the search (Example: com, ca, com.mx, etc.) for localization.
add_htmlNoWhether to return the HTML along with the product details.
store_idNoSpecific Walmart store ID for localization.
product_idYesThe unique identifier for the Walmart product.
screenshotNoForce a browser screenshot (returns base64 image).
delivery_zipNoThe zip code to use for delivery localization.
light_requestNoWhether to use a light request or not.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true, so the description carries most of the burden. It adds genuinely useful behavior: this hits an external scraping provider, handles exactly one query per call, and returns results into the conversation (a context-cost consequence). It omits credit consumption, anti-bot failure modes, and latency, which keeps it from a 5.

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?

Two sentences, front-loaded with the core action before the scope constraint. The CLI pointer is a bit tangential to invoking this tool but is short and actionable, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full parameter coverage, the remaining gaps are operational: no mention of ScrapingBee credit cost, rate limits, or what happens on blocked/failed scrapes. For a nine-parameter scraping tool with only a readOnlyHint annotation, that leaves the agent under-informed about failure and cost behavior.

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% and all nine parameters (device, domain, store_id, delivery_zip, add_html, screenshot, light_request, tag, product_id) are documented in the schema. The description adds no additional meaning about any of them, so the baseline of 3 is correct.

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?

The description opens with a specific verb+resource+provider: 'Scrape Walmart product details using ScrapingBee.' That clearly separates it from get_walmart_search_results and get_amazon_product_details by resource and site. It stops short of explicitly naming any sibling, so it lands just under 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 Guidelines3/5

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

It states a real usage constraint ('one query per call') and points to an alternative (the ScrapingBee CLI) for batching or writing to disk. However, that alternative is a CLI rather than a sibling tool, and there is no guidance on when to prefer get_walmart_search_results, get_page_html, or extract_page_data over this. Usage context is implied rather than routed.

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