Crawlora MCP

grailed_seller

Read-only

A Grailed seller's public profile plus a page of their current active listings (Grailed's own "shop" view of a seller). username is the seller's Grailed username, from a listing's own seller.username field. Listings only ever contains that seller's ACTIVE listings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "grailed_seller"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based page number for the seller's listings, defaults to 1
`limit`	No	Listings per page, defaults to 24, maximum 100
`username`	Yes	Grailed username

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Listings per page, defaults to 24, maximum 100"
```
- addedInput schema / properties / page / description
```
Added value: +"One-based page number for the seller's listings, defaults to 1"
```
- addedInput schema / properties / username / description
```
Added value: +"Grailed username"
```
First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, so the safety profile is settled. The description adds a genuinely useful behavioral constraint not in the structured data: Listings only ever contains ACTIVE listings, clarifying what the returned page will and will not include.

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 tight sentences, front-loaded with what the tool returns and its scope. No filler; every clause (shop view, username provenance, active-only) earns its place.

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

Completeness5/5

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

With an output schema present, the description needn't explain return values, and it covers the tool's purpose, input provenance, and a non-obvious scope constraint. Nothing an agent needs to call it correctly is missing.

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 page and limit are fully documented in the schema and need no compensation. The description adds provenance meaning for username, but that is a modest supplement rather than filling a documentation gap.

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+resource: returns a Grailed seller's public profile plus a page of their active listings, and explicitly names the underlying view ('Grailed's own shop view'). This distinguishes it from grailed_search and grailed_seller_reviews without needing to open 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 Guidelines3/5

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

It gives a useful sourcing hint for the username (from a listing's own seller.username field) and implies active-only scope, which hints at using grailed_sold_listings for sold items. However, it never explicitly states when to use this versus grailed_seller_reviews or grailed_sold_listings, leaving the routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?