Skip to main content
Glama

Wayfair Product

run_wayfair_products
Read-onlyIdempotent

Get full Wayfair product details by SKU (or product URL): title, brand, price, list price, discount, rating with per-star breakdown, images, variants, verified status, availability and category. Flat 5 points per successful run.

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": "<product>"
    },
    "name": "run_wayfair_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesSKU or product URL. e.g. W114765796

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavioral context beyond them: a 'Flat 5 points per successful run' cost disclosure and the fact that the payload includes verified status and availability, alerting the agent to per-call pricing.

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?

One front-loaded sentence plus a short cost note; nothing is wasted. The long field enumeration is slightly list-heavy but each item conveys what the call returns.

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?

There is no output schema, and the description compensates by enumerating the returned fields (price, discounts, rating breakdown, images, variants, availability). Combined with the cost note and the annotations, an agent has enough to call and price the operation, though error/not-found behavior is unstated.

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 coverage is 100% and the single parameter already documents 'SKU or product URL' with an example. The description's parenthetical matches the schema without adding format or validation detail, 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 ('Get') and resource ('full Wayfair product details') and even enumerates the returned fields. The 'by SKU (or product URL)' clause distinguishes it from run_wayfair_products_search, which takes query terms rather than an identifier.

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

Usage Guidelines3/5

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

Usage is only implied by the required identifier: it is clear you call this when you already have a SKU or product URL, but there is no explicit when/when-not framing and no pointer to run_wayfair_products_search for discovery or run_wayfair_sellers for seller data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources