Crawlora MCP

walmart_product_reviews

Read-only

Fetch the on-page Walmart review snapshot for one product, including rating distribution and a sample of recent review items; this is not a full paginated feed. Use walmart_product for product details or walmart_search to find a 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": {
      "item_id": "<item_id>"
    },
    "name": "walmart_product_reviews"
  }
}

Input Schema

Name	Required	Description	Default
`item_id`	Yes	Walmart item id (the numeric id in a /ip/{id} URL)

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.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / item_id / description
```
Added value: +"Walmart item id (the numeric id in a /ip/{id} URL)"
```
First observedOct 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Adds substantive context beyond the annotations: the description discloses that this returns a snapshot with limited sample size and is not a paginated feed, which is the key behavioral caveat. Annotations already cover readOnly/harmless, so the description's scope disclosure is the real value. It doesn't mention caching or update frequency, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded detection of scope, then routing alternatives. No filler; every clause earns its place.

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?

For a single-param read tool with an output schema, annotations, and full schema coverage, the description supplies exactly the missing piece, scope and the sample-vs-feed distinction, and names alternative tools. Nothing needed to invoke correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema itself explains the item_id format (/ip/{id} URL). Description adds no parameter detail, but with a single fully-documented parameter the baseline of 4 applies; no gap to compensate for.

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 (Fetch) and scoped resource (Walmart on-page review snapshot for one product), and immediately specifies the scope: rating distribution plus a sample of recent review items, explicitly not a full paginated feed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly names both alternatives (walmart_product for product details, walmart_search to find a product) and states the boundary condition that this is not a full paginated feed, routing the agent correctly.

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.