Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

therealreal_designer

Browse The RealReal listings by designer slug, with pagination and filters for on-sale or available items, to find current inventory for a specific designer.

Instructions

Browse The RealReal listings by designer. Returns a page of 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.

Input Schema

NameRequiredDescriptionDefault
slugYesDesigner slug, from the designers endpoint's slug field
afterNoOpaque pagination cursor from a previous response's next_after. Omit for the first page
on_saleNoOnly return items currently marked down from their original price
availableNoOnly return items currently available to purchase (excludes sold and waitlisted items)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 discloses the key non-obvious behavior: results are paginated ('Returns a page') and are advanced via an opaque cursor returned as next_after. The browser is self-evidently read-only, so the remaining gaps (permissions, rate limits, result shape) are minor.

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 short, front-loaded sentences with no filler. There is mild redundancy across the first two sentences, which both restate 'The RealReal listings ... by designer,' so it falls just short of maximally tight.

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?

Given no output schema and no annotations, the description covers the essentials: purpose, pagination mechanics, and a slug example. It does not characterize the listing payload or the effect of the on_sale/available filters, but the schema documents those flags, so the definition is nearly complete.

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% and each parameter is already documented in the schema, including the after/next_after relationship. The description reinforces the pagination flow but adds no syntax or meaning beyond what the schema provides for slug, on_sale, or available, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Browse) plus resource (The RealReal listings) and scope (by designer slug), with a concrete example ('e.g. gucci'). It's clear enough to distinguish from generic searches, but it does not name or contrast with sibling tools like therealreal_search or therealreal_designers, which would have made the boundary explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the name and the pagination instructions ('Pass a previous response's next_after back as after'), but there is no explicit when-to-use guidance or exclusion against alternatives such as therealreal_search. The agent must infer that this is the designer-browsing entry point versus a keyword search.

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