Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wayfair_category

Browse a Wayfair category by ID, slug, or URL to retrieve paginated product grids with names, brands, prices, and images.

Instructions

Browse a Wayfair category. Returns a Wayfair category page's product grid, with real page-based pagination. category accepts a bare Wayfair category id ("478390"), a "c"-prefixed id ("c478390"), a category slug ("office-chairs-c478390"), or a full category URL copied from wayfair.com. Returns products with name, brand, pricing, and image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page, 1-based, defaults to 1
categoryYesWayfair category id, slug, or URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose meaningful behavior: it is a read of a category product grid, uses 'real page-based pagination' (clarifying pagination style), and enumerates returned fields. It does not mention auth or rate limits, but for a public catalog browse this is solid disclosure beyond the schema.

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-loaded with purpose, then pagination, then accepted input formats, then returns. Every sentence carries content; a minor redundancy exists between the opening 'product grid' and the closing 'Returns products with name, brand...', but overall it is tight.

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 no output schema and no annotations, the description should cover returns and behavior, and it does: pagination semantics, input formats, and returned fields (name, brand, pricing, image). What an agent needs to call it is essentially present.

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%, so baseline is 3, but the description adds genuine meaning: it enumerates the accepted formats for `category` (bare id, 'c'-prefixed id, slug, or full URL) with concrete examples, which the schema only summarizes as 'id, slug, or URL'. The `page` parameter is left to the schema.

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?

States a concrete verb+resource ('Browse a Wayfair category') and immediately scopes the output as a category page's product grid, which an agent can distinguish from wayfair_product (single item) and wayfair_categories (category listing). It stops short of naming a sibling to route against, but the scope is unambiguous.

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 implied by the description (use it to see products inside a category) but there is no explicit when-to-use, when-not, or alternative routing versus wayfair_categories or wayfair_product. An agent can infer the fit, but nothing is spelled out.

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