Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

therealreal_collections

Fetch The RealReal curated collection slugs, including editorial and sale-campaign identifiers, to query the collection endpoint directly.

Instructions

Get The RealReal curated collection slugs. Returns The RealReal's full published set of curated editorial and sale-campaign collection slugs (e.g. on-sale-now, hermes-birkin-bag), each usable directly against the collection endpoint's own slug field. This is reference data that changes rarely, so responses are cached.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the disclosure burden and does add real behavioral context: it is a read/reference operation, the underlying data changes rarely, and responses are cached (implying possible staleness). It leaves auth requirements and result size/format unspecified, which keeps it out of the top score.

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?

Three tight sentences, front-loaded with what is returned, then the example/usage mapping, then the caching note. Every sentence adds information, and there is no filler.

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 no-parameter reference-list tool with no output schema and no annotations, the description covers what the agent needs: the nature of the payload, the slug format with examples, and the caching behavior. Only minor gaps remain (e.g., payload size or auth), so it is close to complete.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals the no-input nature by describing output only.

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 (Get) and resource (The RealReal curated collection slugs), and specifies the exact output — the full published set of curated editorial and sale-campaign slugs with concrete examples (on-sale-now, hermes-birkin-bag). It also distinguishes itself from the sibling collection endpoint by noting the slugs are usable against that endpoint's slug field, so an agent can route without ambiguity.

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?

The description explains the role of the returned data — these slugs feed the collection endpoint — which effectively tells the agent when to reach for this tool before calling a collection lookup. It doesn't explicitly name forbidden cases or alternatives, so it stops short of the top tier, but the usage context is clear.

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