Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

grailed_search

Search and browse active Grailed resale listings by keyword, designer, category, size, color, condition, department, and price range, with sort options.

Instructions

Search or browse Grailed active listings. Searches or browses Grailed's (grailed.com) peer-to-peer resale marketplace for currently-active listings. q, designer, department, category, size, color, condition, min_price, and max_price are all optional and combine as an AND -- a free-text q can be combined with any of the facet filters in the same request, or every field can be omitted to browse the full active catalog by Grailed's own "heat" relevance ranking. designer accepts one of the values grailed-designers' own designers[].name field returns; department, category, size, and color accept values from grailed-categories' own departments[].value/categories[].value/sizes[].value/colors[].value fields. condition and sort are fixed, closed enums (listed below). Keyword search uses typo-tolerant relevance ranking, not a guaranteed exact match. A query with genuinely zero matches returns a well-formed empty result rather than an error.

Input 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 heat
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 price (inclusive), in USD
min_priceNoMinimum price (inclusive), in USD
departmentNoDepartment filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations the description carries the full burden and delivers: typo-tolerant relevance ranking (not guaranteed exact match), a well-formed empty result instead of an error on zero matches, and default heat ranking. It omits auth/permission and pagination behavior, but the disclosed behavioral traits are well above baseline.

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?

Reasonably sized and front-loaded with the core purpose first, then the field descriptions. Some mild redundancy in restating the search purpose and parameter list, but every sentence contributes substantive information.

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 12-param, no-required-arg search tool with no output schema, the description covers enough: defaults, enum constraints, facet value sources, ranking behavior, and empty-result handling. Return shape is the only notable gap, which is acceptable given no output schema.

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%, so baseline is 3, but the description adds real value: it states condition and sort are closed enums, explains that designer values come from grailed-designers' designers[].name and category facets from grailed-categories, and clarifies the AND combination semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'Search or browse Grailed active listings' and clarifies it's grailed.com's peer-to-peer resale marketplace for currently-active listings. The 'currently-active' qualifier implicitly separates it from siblings like grailed_sold_listings, but no sibling is named explicitly.

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 that all filters are optional and combine as AND, that a free-text q can be mixed with facets, and that omitting everything browses the full active catalog by heat. It also routes the agent to grailed-designers and grailed-categories for valid facet values. No explicit 'when-not-to-use' or named alternative, so it stops short of a 5.

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