Crawlora MCP

wayfair_product

Read-only

One Wayfair product's full detail: name, brand, price, stock status, aggregate rating with a 1-5 star breakdown, images, every selectable variant option (e.g. color, finish), and site-selected feature highlights. product_id is the product's own "W"-prefixed id, taken from a category result's product_id field or a product page's URL. An unrecognized product_id returns not found.

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": "wayfair_product"
  }
}

Input Schema

Name	Required	Description	Default
`product_id`	Yes	Required Wayfair product ID in W followed by 1–15 digits, from wayfair_category or a product page URL; an unknown ID returns not found.

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 9, 2026

addedInput schema / properties / product_id / description

Added value: +"Required Wayfair product ID in W followed by 1–15 digits, from wayfair_category or a product page URL; an unknown ID returns not found."

First observedOct 7, 2026

TDQS

A4.2/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 behavioral context beyond the annotations: an unrecognized product_id yields an error ('returns not found'). It does not cover rate limits or auth, but the error semantics are the key addition for a lookup tool.

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, purpose front-loaded, followed by ID sourcing and error behavior. The content-field list is dense but each item is informative; the second sentence (ID sourcing) slightly overlaps the schema, keeping it from a 5.

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 one required parameter, an output schema covering return values, and read-only annotations, the description supplies everything needed: purpose, ID provenance, and the not-found failure mode. Nothing an agent needs to call it correctly is missing.

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 the schema field already states the W-prefix, digit range, source (wayfair_category/URL), and not-found behavior. The description largely repeats this, adding little beyond what structured data provides; baseline 3 is appropriate.

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+resource ('One Wayfair product's full detail') and enumerates the returned content, so the agent knows exactly what it retrieves. It is clearly distinguishable from siblings wayfair_categories and wayfair_category, which are browse tools rather than detail lookups.

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?

Explains where product_id comes from ('a category result's product_id field or a product page's URL'), which implicitly tells the agent to obtain IDs via category browsing first. It gives clear context but no explicit when-not-to-use or named alternative selection rule.

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.