Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

therealreal_category

Browse The RealReal listings by category path, with optional sale or availability filters and cursor-based pagination for next pages.

Instructions

Browse The RealReal listings by category. Returns a page of The RealReal listings browsed by category (taxon) permalink path, e.g. women/handbags. Pass a previous response's next_after back as after to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
pathYesCategory permalink path, from the categories endpoint's permalink 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.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the pagination contract (passing a prior response's next_after as after), which is useful, but says nothing about page size, ordering, auth requirements, rate limits, or what a result item contains.

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 sentences, front-loaded with the purpose, and every sentence carries information. There is mild redundancy between 'Browse...by category' and 'listings browsed by category (taxon) permalink path,' but it stays 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?

There is no output schema and no annotations, so the description has to stand alone. It covers the category input source and pagination loop, which is most of what an agent needs for a simple browse call, though result shape and ordering remain unaddressed.

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 description coverage is 100%, so the schema already documents all four parameters, setting the baseline at 3. The description adds only the concrete example 'women/handbags' for path and restates the next_after-to-after relationship that the schema already describes.

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?

The description states a specific verb and resource: 'Browse The RealReal listings by category,' and clarifies that browsing is driven by a category (taxon) permalink path. This is clear enough to distinguish it from therealreal_search or therealreal_listing, though it does not explicitly name those siblings.

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?

It implies usage (browse a category path obtained from the categories endpoint) and explains how to paginate, but never says when to prefer this over therealreal_search or therealreal_collection(s), nor when-not to use it. Guidance 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.

Deploy Server

Other Tools