Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

therealreal_autocomplete

Get The RealReal search-box suggestions for any partial query. Returns typeahead results from the public first-party catalog API.

Instructions

Get The RealReal search-box suggestions. Returns The RealReal's own search-box typeahead suggestions for a partial query. Credential-free public data sourced from The RealReal's own first-party catalog API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesPartial free-text query to get search-box suggestions for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations are absent, so the description carries the full burden. It does disclose that the data is credential-free, public, and sourced from The RealReal's own first-party catalog API, which is useful. However, it doesn't describe the response format, potential limits, or any other operational behavior beyond the basic read operation.

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 sentences, front-loaded with the core action. The first two sentences are slightly redundant, but each adds a detail (typeahead, partial query, credential-free source).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-annotation tool, the description covers the essential behavior and data source. It lacks an explicit statement of the return value shape, but for search-box suggestions this is a minor gap.

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% and the single 'term' parameter is already described as a partial free-text query. The description reinforces this but doesn't add new semantic information beyond what the schema provides, earning the baseline 3.

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 uses a specific verb ('Get') and a distinct resource ('The RealReal search-box suggestions'), and clarifies the behavior as typeahead suggestions for a partial query. It doesn't explicitly name sibling tools like therealreal_search, but the 'search-box' phrasing makes the distinction reasonably clear.

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 clearly implies the use case: when an agent has a partial free-text query and needs autocomplete suggestions. It gives clear context but doesn't explicitly mention when not to use it or name alternative tools such as therealreal_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