Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

grailed_sold_listings

Retrieve Grailed sale price history from sold listings, including final sale prices and dates. Filter by designer, category, size, color, condition, and sold-price range for comparable-sales lookups.

Instructions

Search Grailed sold listings (sale price history). Searches Grailed's SOLD-listing index -- a separate dataset from active listings, carrying each item's final sale price and sale date. Same filter shape as grailed-search (q, designer, department, category, size, color, condition), but min_price/max_price filter the SOLD price, not the original asking price. Useful for sale-price-history/comparable-sales lookups (e.g. "what did this designer/category actually sell for recently"). A query with genuinely zero matches returns a well-formed empty result rather than an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search query
pageNoOne-based page number, defaults to 1
sizeNoSize facet filter, from grailed-categories' own sizes[].value field
sortNoSort order, defaults to recent
colorNoColor facet filter, from grailed-categories' own colors[].value field
limitNoResults per page, defaults to 24, maximum 100
categoryNoCategory facet filter, from grailed-categories' own categories[].value field
designerNoDesigner/brand name filter, from grailed-designers' own designers[].name field
conditionNoCondition filter
max_priceNoMaximum SOLD price (inclusive), in USD
min_priceNoMinimum SOLD price (inclusive), in USD
departmentNoDepartment filter

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 full behavioral burden. It discloses that this searches a separate SOLD-listing dataset, that min/max_price apply to the sold price, and that zero matches return a well-formed empty result rather than an error. It does not cover pagination or rate limits, but the core behavioral traits are clearly stated.

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?

Four sentences, front-loaded with the core purpose, and every sentence earns its place: dataset distinction, filter semantics, use case, and empty-result behavior. No fluff or repetition of schema content.

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?

Given no annotations and no output schema, the description covers the essential context: what dataset is searched, how price filters differ, when to use it, and empty-result behavior. It could additionally describe pagination or return fields, but the description is strong enough for an agent to invoke the tool correctly.

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 baseline is 3. The description reinforces that min_price/max_price filter the SOLD price rather than the asking price, but the schema already states 'Maximum SOLD price (inclusive)' and 'Minimum SOLD price (inclusive).' No new parameter meaning is added beyond what the schema provides.

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?

The description opens with a specific verb and resource: 'Search Grailed sold listings (sale price history).' It explicitly distinguishes this from active listings and names the sibling grailed-search, so an agent can tell them apart immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names the alternative (grailed-search), explains the key difference (sold price vs. asking price), and gives concrete use cases ('sale-price-history/comparable-sales lookups'). This is explicit when-to-use guidance with an alternative.

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