Skip to main content
Glama
E-commerce Search & Rankings MCP

E-commerce Search & Rankings MCP

Walmart Fast Product Scraper

e-commerce--walmart-fast-product-scraper
Read-only

Scrape Walmart.com and Walmart.ca search or category pages to collect product names, prices, availability, ratings, and sellers as structured JSON for comparison and analysis.

Instructions

Walmart Fast Product Scraper. Scrape product data from Walmart.com and Walmart.ca search and category pages, including name, priceInfo, availability, averageRating, and sellerName. Export data, run via API, schedule and monitor runs, or integrate with other tools.

When to use: Use when you need Walmart.com or Walmart.ca search or category results with price, availability, rating and seller.

Returns: the run's dataset rows as structured JSON (one row per result), plus the run and dataset IDs for paging the full dataset.

Behavior: starts one run of the Apify Actor "e-commerce/walmart-fast-product-scraper" through Apify's hosted MCP gateway (mcp.apify.com) with your own APIFY_TOKEN; the run uses your Apify account. Read-only: it only reads public web data and changes nothing on the source site. Docs: https://apify.com/e-commerce/walmart-fast-product-scraper

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": {
      "startUrls": "<startUrls>"
    },
    "name": "e-commerce--walmart-fast-product-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
startUrlsYesOne or more Walmart search or category page URLs to scrape, for example https://walmart.com/search?q=tshirt. Each page is read in listing order, and its products are collected up to the limit set in Max products (per start URL).
maxProductsPerStartUrlNoThe maximum number of products to scrape from each start URL, for example 10. Products are collected in listing order until this limit is reached. Example: 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-idempotent/non-destructive, but the description adds genuinely new context: it starts a run of a named Apify Actor through the mcp.apify.com gateway, requires the caller's own APIFY_TOKEN, consumes the caller's Apify account, and creates run and dataset records. It also clarifies that 'read-only' refers to the source site, resolving what would otherwise look like a tension with the account-side writes. It does not mention rate limits, run duration, or cost.

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?

Front-loaded and segmented with When to use / Returns / Behavior / Docs, which is easy to scan. Minor waste: the leading 'Walmart Fast Product Scraper.' restates the title, and the marketing line 'Export data, run via API, schedule and monitor runs, or integrate with other tools' does not help an agent decide or call correctly.

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?

With only two parameters and no output schema, the description covers everything an agent needs: input expectation (search/category URLs), return shape (one JSON row per result plus run and dataset IDs for paging), execution model, and auth requirement. Nothing material is left for the caller to guess.

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%, with both startUrls and maxProductsPerStartUrl documented in the schema including an example URL and the listing-order collection rule. The description adds no parameter-level meaning beyond that, so the 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?

States a specific verb and resource: scrape Walmart.com and Walmart.ca search and category pages, and enumerates the extracted fields (name, priceInfo, availability, averageRating, sellerName). The marketplace domain alone separates it from every listed sibling (Amazon, eBay, AliExpress, Etsy, Google Shopping, Shopify).

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?

An explicit 'When to use' line scopes it to Walmart search or category results with price, availability, rating and seller. It gives no when-not conditions or named alternatives among the sibling marketplace scrapers, so the agent must infer that other retailers are out of scope.

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