Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

therealreal_similar

Fetch The RealReal visual-similarity recommendations by numeric product ID to discover comparable items and alternatives from a listing response.

Instructions

Get The RealReal similar-item recommendations. Returns The RealReal's own "Similar Items" visual-similarity recommendations for one product, looked up by the product's numeric id (from any other The RealReal endpoint's listing response id field).

Input Schema

NameRequiredDescriptionDefault
product_idYesThe RealReal numeric product id, from a search/category/designer/listing/collection response's id field

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 full behavioral burden. It discloses that the payload is The RealReal's own visual-similarity output rather than a generic or computed recommendation, which is useful, but says nothing about permissions, rate limits, or response shape.

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?

Two front-loaded sentences that lead with what the tool returns before explaining the input. There is mild redundancy between 'similar-item recommendations' and the repeated 'Similar Items' phrasing, but nothing is bloated.

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 single-parameter read tool with no annotations and no output schema, the description covers what is returned, whose recommendations they are, and where the id must come from. Only the safety profile and response shape are left implicit.

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 required product_id is already documented. The description restates the id's origin ('from any other The RealReal endpoint's listing response id field'), which largely duplicates the schema's own wording rather than adding new meaning.

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 (similar-item recommendations) and narrows the scope to The RealReal's own visual-similarity recommendations for a single product. An agent can distinguish this from siblings like therealreal_listing or therealreal_search without opening a schema.

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 tells the agent how to obtain the required input (the numeric id from any other The RealReal endpoint's listing response), which is real usage context. It stops short of stating when to prefer this tool over alternatives, so no exclusions are given.

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