Besot: Musician Fashion Resale

search_pieces

Read-onlyIdempotent

Find where to buy a specific piece of clothing or footwear connected to the people we obsess over, and get every live resale listing for it in one call.

Use this when someone asks questions like: where can I buy the Gucci HA HA HA blazer; is the Ivy Park Drip 2 hoodie listed in a medium; what is the Pleasing crewneck going for right now; which platforms have the Oasis adidas Original Forever trainers in a UK 9; what Beatles Comme des Garcons pieces are on the resale market today.

Most of these garments are sold out at retail and exist only on resale, scattered across marketplaces under inconsistent seller titles. besot gives each garment one canonical name and pulls the live listings for that exact piece from eBay, StockX, GOAT, The RealReal, Vestiaire, Grailed, Poshmark and Depop.

Covers clothing and footwear that the people we obsess over designed, founded, were the inspiration for, or wore. Takes plain language in q (for example "Ivy Park Drip 2 hoodie" or "Harry Styles Gucci blazer"), with optional filters for artist, brand, collection, garment type, size, condition, source platform, and price range.

Every listing returned carries the platform, size, condition, price (approximate USD, null when the seller did not state one), and a direct buy link.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Free text over piece name, collection, artist, brand, and garment vocabulary. Product names are canonical (Gazelle, Firebird Track Top), so plain garment words work too, in British or American English: trainers or sneakers, jumper or sweater, trousers or pants, trackie or tracksuit.
`size`	No	Match a listing size; call get_facets for valid values
`sort`	No
`type`	No	COLLECTION type: Collab, Capsule, or Own brand. For the garment, use category.
`brand`	No	Designer/brand name
`limit`	No	1-50, default 20
`artist`	No
`source`	No	Resale platform, e.g. ebay, grailed, therealreal
`category`	No	GARMENT category, one of: footwear, outerwear, tops, knitwear, hoodies, bottoms, one-pieces, suits, sets, accessories, eyewear, swim-active
`maxPrice`	No
`minPrice`	No
`condition`	No
`collection`	No	Collection id (exact)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJul 13, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "GARMENT category, one of: footwear, outerwear, tops, knitwear, hoodies, bottoms, one-pieces, suits, sets, accessories, eyewear, swim-active",
+  "maxLength": 100,
+  "type": "string"
+}

changedInput schema / properties / q / description

Previous value: -"Free text over piece name, collection, artist, brand"New value: +"Free text over piece name, collection, artist, brand, and garment vocabulary. Product names are canonical (Gazelle, Firebird Track Top), so plain garment words work too, in British or American English: trainers or sneakers, jumper or sweater, trousers or pants, trackie or tracksuit."

changedInput schema / properties / type / description

Previous value: -"Collab, Capsule, or Own brand"New value: +"COLLECTION type: Collab, Capsule, or Own brand. For the garment, use category."

Changed9 schema fields changedJul 6, 2026
- addedInput schema / properties / artist / maxLength
```
Added value: +200
```
- addedInput schema / properties / brand / maxLength
```
Added value: +200
```
- addedInput schema / properties / collection / maxLength
```
Added value: +200
```
- addedInput schema / properties / condition / maxLength
```
Added value: +100
```
- addedInput schema / properties / q / maxLength
```
Added value: +500
```
- addedInput schema / properties / size / maxLength
```
Added value: +100
```
- addedInput schema / properties / sort / maxLength
```
Added value: +100
```
- addedInput schema / properties / source / maxLength
```
Added value: +200
```
- addedInput schema / properties / type / maxLength
```
Added value: +100
```
First observedJun 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses canonical naming, aggregation across eight resale marketplaces, and the exact fields returned including null price behavior. Minor overstatement: 'every live resale listing' is not reconciled with the limit parameter that defaults to 20, and pagination is not mentioned.

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 and use-case examples, with clear paragraph breaks and no buried critical info. It is a little wordy in the background paragraph and repeats 'live resale' and the filter list, so not maximally concise.

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?

For a 13-parameter search tool with no output schema, this is unusually complete: scope, query form, filter dimensions, platform coverage, and returned listing fields are all specified. Schema defaults and enum values cover the remaining details.

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?

With 62% schema coverage, the description compensates by explaining that q takes plain language, giving examples, and listing the eight optional filter dimensions (artist, brand, collection, garment type, size, condition, source, price range). It doesn't add meaning for sort, but the enum schema covers that.

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?

Opens with a specific verb and resource: 'Find where to buy a specific piece of clothing or footwear connected to the people we obsess over, and get every live resale listing for it in one call.' Concrete example queries and the explicit platform scope make it clearly distinct from siblings like get_piece and get_facets.

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?

Explicitly says 'Use this when someone asks questions like…' and gives four realistic queries that map directly to q. It does not state exclusions or explicitly route to sibling tools, though the schema mentions get_facets for size values, so it lacks full when-not guidance.

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

All Besot: Musician Fashion Resale 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?