Crawlora MCP

walmart_search

Read-only

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. q: Search query. Use walmart_product to get a Walmart product.

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": {
      "q": "<q>"
    },
    "name": "walmart_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search query
`page`	No	1-based page number (default 1)
`sort`	No	Sort order. Documented values: best_match, price_low, price_high, best_seller, new_arrivals, rating_high.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / page / description
```
Added value: +"1-based page number (default 1)"
```
addedInput schema / properties / q / description
```
Added value: +"Search query"
```

addedInput schema / properties / sort / description

Added value: +"Sort order. Documented values: best_match, price_low, price_high, best_seller, new_arrivals, rating_high."

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new context beyond them: the data is credential-free public Walmart data rendered from the search page via proxied browser renderers, which signals no auth and a scraped/render-based origin. It doesn't cover rate limits or paging behavior, keeping it at 4.

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-loads the return fields in one sentence, then the sourcing note, then the routing hint. Slightly padded by restating 'q: Search query' already in the schema, but overall tight and well-ordered.

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?

With an output schema present, return values need no further explanation, and the sourcing/auth note plus sibling routing cover the key decision points. A note on paging limits or result volume would have made it fully complete.

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%, so q, page, and sort are already documented in the schema. The description only restates 'q: Search query' and adds nothing about pagination or sort semantics beyond what the schema lists, 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 ('Returns Walmart search results') and enumerates the returned fields (item id, title, brand, price, image, availability, seller, rating). It differentiates itself from the sibling walmart_product by naming it explicitly, so an agent can route without opening either schema.

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?

Provides a clear alternative ('Use walmart_product to get a Walmart product'), giving the agent a routing condition. It stops short of explicit when-to-use/when-not framing or notes about when paging/sorting is warranted, so it clears the bar but isn't exhaustive.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.