Crawlora MCP

therealreal_collection

Read-only

The RealReal listings browsed by curated collection slug (e.g. on-sale-now) -- sale campaigns, editor's picks, and similar merchandising collections distinct from category/designer browsing.

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_collection"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Collection slug, from the collections endpoint's slug field.
`after`	No	Opaque pagination cursor from a previous response's next_after. Omit for the first page.

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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are merchandising listings rather than category/designer content, but says nothing about result volume, pagination behavior, or freshness beyond what the schema and annotations provide.

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?

A single front-loaded sentence with no filler; the em-dash clause earns its place by defining the scope boundary. Nothing is repeated from the schema or annotations.

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 need no explanation, and annotations carry the safety profile. For a 2-param read tool the description covers purpose and scope adequately, though a hint on pagination size or collection discovery would round it out.

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 the schema already documents both parameters, making 3 the baseline. The description adds a concrete example slug ('on-sale-now'), which gives the agent a usable value shape that the schema's generic 'slug field' wording does not.

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?

Names a specific verb+resource (listings browsed by curated collection slug) and immediately scopes it with an example ('on-sale-now'). The trailing clause explicitly separates it from category/designer browsing, so an agent can distinguish it from therealreal_category and therealreal_designer 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?

Gives clear context for when this applies (sale campaigns, editor's picks, merchandising collections) and implies the exclusion of category/designer browsing. It stops short of naming the concrete alternative tool (e.g. therealreal_collections for enumerating slugs), so the routing is implied rather than explicit.

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?