Crawlora MCP

therealreal_designer

Read-only

Returns a page of normalized The RealReal listings browsed by designer slug, e.g. gucci. Pass a previous response's next_after back as after to fetch the next page. Credential-free public data sourced from The RealReal's own server-rendered designer page. available: Only return items currently available to purchase (excludes sold and waitlisted items). on_sale: Only return items currently marked down from their original price. Use therealreal_designers to get The RealReal designer directory.

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": {
      "slug": "<slug>"
    },
    "name": "therealreal_designer"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Designer slug, from the designers endpoint's slug field.
`after`	No	Opaque pagination cursor from a previous response's next_after. Omit for the first page.
`on_sale`	No	Only return items currently marked down from their original price.
`available`	No	Only return items currently available to purchase (excludes sold and waitlisted items).

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

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: 'Credential-free public data sourced from The RealReal's own server-rendered designer page,' plus pagination behavior and the filter semantics of available/on_sale.

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?

The core purpose is front-loaded in the first sentence, and the pagination hint follows immediately. It is appropriately sized, though the available/on_sale definitions duplicate the schema text verbatim, a minor redundancy.

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 an output schema present, return values needn't be explained, and the description still covers data provenance, pagination, filters, and the sibling needed to find slugs. It is complete for calling the tool; only the relationship to the search/collection siblings is left implicit.

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 schema already documents slug, after, available, and on_sale. The description largely restates those definitions ('excludes sold and waitlisted items', 'marked down from their original price') and the after cursor usage, adding little 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 and resource ('Returns a page of normalized The RealReal listings browsed by designer slug') with an example ('e.g. gucci'), so an agent knows exactly what it produces. It also relates to a named sibling (therealreal_designers) and, via 'browsed by designer slug,' implicitly separates itself from therealreal_search and therealreal_collection.

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?

It gives clear operational context: pass next_after back as after for pagination, and use therealreal_designers to obtain valid slugs (a prerequisite sibling). It does not explicitly state when to prefer this over therealreal_search or therealreal_collection, so it lacks true exclusions, but the 'how to call it' guidance is strong.

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.

Resources

Need Help?