Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

grailed_listing

Fetch a complete Grailed listing by its numeric ID, returning full details: description, photos, measurements, designers, and seller profile.

Instructions

Get a Grailed listing. Returns full normalized listing-detail data for one Grailed listing: description, every photo, measurements, designers, and the seller's full profile -- richer than the flattened summary grailed-search/grailed-sold-listings return per listing. id is the listing's numeric id, from a search or sold-listings result's own listings[].id field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesListing id, from a search or sold-listings result's own listings[].id field

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, the description carries the burden of describing behavior. It states it returns 'full normalized listing-detail data' and lists main fields, which is transparent about output. It doesn't cover error cases or side effects, but for a read-only get, that's acceptable. No contradictions with annotations (none provided).

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?

Two sentences, front-loaded with purpose and return contents, then a precise explanation of the id parameter. No fluff or redundancy; every sentence adds value.

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?

Without an output schema, the description sufficiently outlines the return data (description, photos, measurements, designers, seller profile) and notes it is richer than search results. It does not enumerate every field (e.g., price, condition) but says 'full normalized listing-detail data', which is adequate for an agent deciding to call it.

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?

Schema coverage is 100% and the description reinforces the id parameter's meaning and origin (numeric id from search/sold-listings listings[].id). It adds clarity about the id's type and source, going slightly beyond the schema description.

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 clearly states the tool fetches a Grailed listing and enumerates the exact fields returned (description, photos, measurements, designers, seller profile). It explicitly contrasts itself with grailed-search/grailed-sold-listings, making its purpose distinct from sibling tools.

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?

It explains that the id comes from a search or sold-listings result, providing clear context on when to use this tool (when full details are needed after getting an id). It does not explicitly mention alternatives for other scenarios, but the source-of-id guidance is helpful.

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