Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

therealreal_collection

Browse The RealReal curated collections by slug, such as sale campaigns or editor's picks, and fetch paginated listings using an after cursor.

Instructions

Browse The RealReal listings by curated collection. Returns a page of 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. Pass a previous response's next_after back as after to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
slugYesCollection slug, from the collections endpoint's slug field
afterNoOpaque pagination cursor from a previous response's next_after. Omit for the first page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that it returns a page of listings and how cursor pagination works, which is useful, but says nothing about auth requirements, rate limits, or result size/shape beyond 'a page'.

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?

Front-loaded with the core purpose and kept to three sentences. Slight redundancy in repeating 'The RealReal listings' and re-explaining the cursor, but overall efficient.

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?

For a two-param, no-annotation, no-output-schema browse tool, the description covers what it returns and how to paginate, which is most of what an agent needs. Missing only peripheral details like result size or auth, which are minor for a read browse.

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 both params are already documented in the schema. The description's mention of next_after/after simply restates the schema's pagination contract, adding little beyond it. 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 (browse) and resource (The RealReal listings by curated collection) and explicitly distinguishes this from category/designer browsing. An agent can differentiate it from therealreal_categories and therealreal_designers without opening schemas.

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: use this for merchandising collections like sale campaigns and editor's picks, as opposed to category/designer browsing. It also explains the pagination workflow (pass next_after back as after). It stops short of naming the sibling collection-listing tool, but the guidance is concrete.

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