Crawlora MCP

therealreal_search

Read-only

Search The RealReal consignment listings by text, category, designer, condition, and price, returning a count and opaque cursor. Use therealreal_category or therealreal_collection for browse pages or therealreal_listing for one item.

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": {
      "query": "<query>"
    },
    "name": "therealreal_search"
  }
}

Input Schema

Name	Required	Description
`after`	No	Opaque pagination cursor from a previous response's next_after. Omit for the first page.
`query`	Yes	Free-text keyword search. Required -- The RealReal's own /products route only applies category/designer/condition/price filters when a keyword query is also present; without one it serves an unrelated promotional collection instead.
`on_sale`	No	Only return items currently marked down from their original price.
`price_to`	No	Maximum price in USD.
`available`	No	Only return items currently available to purchase (excludes sold and waitlisted items).
`price_from`	No	Minimum price in USD.
`category_id`	No	Category (taxon) id to filter by, from the categories endpoint's id field.
`designer_id`	No	Designer id to filter by, from the designers endpoint's id field.
`condition_id`	No	Condition grade id to filter by, from the conditions endpoint's id field.

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.

First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so safety is already covered. The description goes beyond that by disclosing the return shape ('a count and opaque cursor'), which signals pagination semantics. It stops short of documenting page-size limits or result caps, so it is useful but not exhaustive.

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 tight sentences. The capability statement is front-loaded and the routing guidance follows, with zero filler text.

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 9 params at full schema coverage, an output schema for the return values, and annotations for the safety profile, the description only needs to state scope and routing. Both are present and the sibling disambiguation is thorough.

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 every parameter is documented in-schema, including the important caveat that RealReal's route needs a keyword query. The description only restates the filter dimensions at a high level, adding no syntax or format meaning beyond the schema. 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 (Search) plus the resource (The RealReal consignment listings) and enumerates the filter dimensions. It also names the sibling tools it is not (therealreal_category, therealreal_collection, therealreal_listing), so an agent can distinguish it from the many adjacent therealreal_* tools 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 Guidelines5/5

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

Explicitly routes the agent: browse pages go to therealreal_category or therealreal_collection, a single item goes to therealreal_listing. This is a clear when-this/when-that rule with named alternatives, leaving nothing to inference.

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.