Crawlora MCP

therealreal_category

Read-only

Browse The RealReal listings under a category permalink such as women/handbags. Use therealreal_categories to find categories, therealreal_search for filtered discovery, or therealreal_collections and therealreal_collection for curated groupings.

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": {
      "path": "<path>"
    },
    "name": "therealreal_category"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Category permalink path, from the categories endpoint's permalink field, e.g. women/handbags.
`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.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 no behavioral context beyond that - no mention of pagination behavior, result volume, or auth/rate characteristics. With annotations carrying the safety burden, this is minimum viable.

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 sentences, front-loaded with the core purpose, followed by compact sibling routing. No filler or 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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. Purpose and routing are complete; the only minor gap is that pagination and filtering behavior are left entirely to the schema.

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 coverage is 100%, so the schema documents all four parameters including the permalink source and pagination cursor. The description reinforces the path format with the `women/handbags` example but adds no semantics for after, on_sale, or available. Baseline 3 when the schema does the heavy lifting.

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 ('Browse The RealReal listings'), adds scope ('under a category permalink'), and distinguishes itself from siblings by naming categories, search, and collections. An agent can tell exactly what this tool does versus therealreal_search or therealreal_collections.

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: use therealreal_categories to find categories, therealreal_search for filtered discovery, and therealreal_collections/collection for curated groupings. This is a clear when-to-use-this-vs-alternatives mapping rather than 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.

Resources

Need Help?