Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

walmart_search

Search Walmart products by query and page with sorting options, returning item IDs, titles, brands, prices, images, availability, sellers, and ratings.

Instructions

Search Walmart products. Returns Walmart search results: item id, title, brand, price, image, availability, seller, and rating per product. Credential-free public Walmart data, rendered from the search page through proxied browser renderers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query
pageNo1-based page number (default 1)
sortNoSort order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "best_match",
+  "price_low",
+  "price_high",
+  "best_seller",
+  "new_arrivals",
+  "rating_high"
+]
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it adds substantive context: data is credential-free, publicly available, and rendered from the search page through proxied browser renderers. This discloses auth requirements and implementation style beyond a bare 'search products' statement. It does not mention rate limits, latency, or potential anti-bot failures, but the provided context is meaningful.

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 compact sentences with the core action front-loaded ('Search Walmart products'). The return-field list and credential-free rendering note are relevant, and there is no filler or repetition.

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?

Since no output schema is present, the description compensates by listing the exact fields returned per product, which is valuable. It also clarifies the public, credential-free nature and the proxied rendering mechanism. It does not describe result array shape, pagination limits, or error behavior, but these are minor gaps for a straightforward search tool.

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?

The input schema describes all three parameters (q, page, sort) with 100% coverage, so the baseline is 3. The description does not add parameter-level semantics beyond the schema; it focuses on result fields rather than q/page/sort details.

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 and resource ('Search Walmart products') and enumerates the returned per-product fields (item id, title, brand, price, image, availability, seller, rating), so an agent understands what the tool retrieves. It does not explicitly contrast with sibling tools like walmart_product or walmart_product_reviews, but the phrase 'search results' distinguishes it as a list-level operation.

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?

No explicit when-to-use or when-not-to-use guidance is provided, and the description does not mention alternatives such as walmart_product or walmart_product_reviews. The only usage hint is 'Credential-free public Walmart data,' which implies no auth setup but does not help an agent decide when this tool is appropriate versus related search/product tools.

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

Deploy Server

Other Tools