Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

therealreal_search

Search The RealReal's authenticated luxury resale catalog by keyword, filter by designer, category, condition, price, and availability, then browse listing summaries with pagination.

Instructions

Search The RealReal luxury consignment listings. Searches The RealReal's authenticated luxury resale catalog by keyword, optionally combined with category, designer, condition-grade, and price-range filters, returning listing summaries (name, designer, condition, price, images) plus the total matching count and an opaque pagination cursor. Pass a previous response's next_after back as after to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
afterNoOpaque pagination cursor from a previous response's next_after. Omit for the first page
queryYesFree-text keyword search
on_saleNoOnly return items currently marked down from their original price
price_toNoMaximum price in USD
availableNoOnly return items currently available to purchase (excludes sold and waitlisted items)
price_fromNoMinimum price in USD
category_idNoCategory (taxon) id, from the categories endpoint's id field
designer_idNoDesigner id, from the designers endpoint's id field
condition_idNoCondition grade id, from the conditions endpoint's id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it proactively discloses the return shape (name, designer, condition, price, images, total match count, opaque cursor) and the pagination contract. It stops short of stating auth requirements, rate limits, or result-cap behavior, but the disclosure is well above average for an annotation-free 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?

Three sentences, front-loaded with purpose and then filters, then pagination mechanics. The opening two sentences restate the verb 'search' somewhat redundantly, but each sentence otherwise carries useful content with no filler.

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, the description correctly takes on the return-value explanation and covers pagination end-to-end. All 9 parameters are documented in the schema, so nothing agent-critical is missing, though edge behaviors (empty results, cursor expiry) are unaddressed.

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 the baseline is 3. The description names the filter dimensions (category, designer, condition-grade, price-range) but adds no format, unit, or id-source guidance beyond what the schema's own parameter descriptions already supply.

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 (search) and resource (The RealReal luxury consignment listings) and clarifies scope: keyword search over an authenticated resale catalog, optionally narrowed by category, designer, condition, and price. An agent can distinguish it from therealreal_listing, therealreal_collection, or therealreal_similar without opening a 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?

Clear context: it explains the keyword-plus-filter combination and gives explicit pagination instructions (pass next_after back as after). It does not, however, name a sibling alternative or state when NOT to use this tool (e.g., for detail lookups), so it falls short of full routing guidance.

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