Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

grailed_listing

Fetch full Grailed listing details by numeric id, including description, photos, measurements, designers, and complete seller profile data.

Instructions

Get a Grailed listing. Returns full 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

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.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the return payload concretely -- 'description, every photo, measurements, designers, and the seller's full profile.' It does not mention permissions, rate limits, or error behavior, but for a read-only detail fetch the key behavioral trait (depth/richness of the payload vs summaries) is well covered.

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?

Front-loaded purpose with supporting detail about the payload and id source, all in two sentences with little waste. The trailing id sentence slightly duplicates the schema field description, keeping it from a perfect score.

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?

With no output schema and no annotations, the description compensates by enumerating the returned fields and contrasting with summary-level siblings, which is enough for an agent to know what it gets. It lacks any note on failure modes or whether the listing id must be valid/active, 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%, so the schema already documents the single id parameter and its source. The description restates the same id guidance (numeric id from listings[].id) but adds no syntax or format detail beyond what the schema provides. Baseline 3 is appropriate.

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 and resource ('Get a Grailed listing') and immediately differentiates scope from siblings by calling out that it is 'richer than the flattened summary grailed-search/grailed-sold-listings return per listing.' An agent can select this over the search/sold-listing tools without opening either 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?

Explains the context of use: fetch a single listing's full detail, with the id sourced 'from a search or sold-listings result's own listings[].id field.' This chains the tool clearly after a search, but it stops short of an explicit when-not or an exhaustive list of alternatives (e.g., grailed_similar_listings, grailed_seller).

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