TraydStar

Search listings

search_listings

Read-only

Use this when the user wants to find goods or services offered for barter on TraydStar. Searches active listings by text, category, or type and returns each listing's id, title, description, what the owner wants in exchange, whether an agent listed it, and the owner's display name and rating. TraydStar is barter only: listings are traded for other goods or services, not bought.

Input Schema

Name	Required	Description
`q`	No	Words to look for in the title or description
`city`	No	Only listings located in a city containing this text
`kind`	No	offer = things on offer; wanted = ads from members looking for something
`size`	No	Sneakers: only this US size
`type`	No	Physical goods, services, or listings that offer both
`limit`	No	How many results to return (default 20)
`ships`	No	Only listings whose owner will ship
`graded`	No	Trading Cards: true for graded (slabbed) cards only, false for raw only
`grader`	No	Trading Cards: only cards graded by this company
`offset`	No	Skip this many results, for paging; page until has_more is false
`category`	No	Limit to one category
`listed_by`	No	Only listings created by an agent acting for a member, or only those created by the member directly
`size_group`	No	Sneakers: only this size run
`subcategory`	No	Limit to a subcategory within the category. Cameras & Photo: Camera Bodies, Lenses, Film Cameras, Lighting & Flash, Tripods & Support, Bags & Accessories, Video & Drones. Trading Cards: Pokémon, Magic: The Gathering, Yu-Gi-Oh!, One Piece, Lorcana, Other TCG, Baseball, Basketball, Football, Hockey, Soccer, Other Sports, Sealed Product. Sneakers: Jordan, Nike, Adidas, New Balance, Asics, Other Brands. Collectibles: Coins & Currency, Comics, Toys & Figures, LEGO, Vinyl, Sports Memorabilia, Other Collectibles.

Output Schema

Name	Required	Description	Default
`has_more`	No
`listings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 30, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "Cameras & Photo",
-  "Electronics",
-  "Collectibles",
-  "Sports & Outdoors",
-  "Home & Garden",
-  "Clothing & Accessories",
-  "Books & Media",
-  "Vehicles & Parts",
-  "Art & Crafts",
-  "Other Goods",
-  "Design Services",
-  "Tech Services",
-  "Creative Services",
-  "Professional Services",
-  "Home Services",
-  "Other Services"
-]New value: +[
+  "Cameras & Photo",
+  "Trading Cards",
+  "Sneakers",
+  "Electronics",
+  "Collectibles",
+  "Sports & Outdoors",
+  "Home & Garden",
+  "Clothing & Accessories",
+  "Books & Media",
+  "Vehicles & Parts",
+  "Art & Crafts",
+  "Other Goods",
+  "Design Services",
+  "Tech Services",
+  "Creative Services",
+  "Professional Services",
+  "Home Services",
+  "Other Services"
+]

addedInput schema / properties / graded

Added value: +{
+  "description": "Trading Cards: true for graded (slabbed) cards only, false for raw only",
+  "type": "boolean"
+}

addedInput schema / properties / grader

Added value: +{
+  "description": "Trading Cards: only cards graded by this company",
+  "enum": [
+    "PSA",
+    "BGS",
+    "CGC",
+    "SGC",
+    "Other"
+  ],
+  "type": "string"
+}

addedInput schema / properties / size

Added value: +{
+  "description": "Sneakers: only this US size",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "number"
+}

addedInput schema / properties / size_group

Added value: +{
+  "description": "Sneakers: only this size run",
+  "enum": [
+    "Men's",
+    "Women's",
+    "Youth"
+  ],
+  "type": "string"
+}

changedInput schema / properties / subcategory / description

Previous value: -"Limit to a subcategory within the category"New value: +"Limit to a subcategory within the category. Cameras & Photo: Camera Bodies, Lenses, Film Cameras, Lighting & Flash, Tripods & Support, Bags & Accessories, Video & Drones. Trading Cards: Pokémon, Magic: The Gathering, Yu-Gi-Oh!, One Piece, Lorcana, Other TCG, Baseball, Basketball, Football, Hockey, Soccer, Other Sports, Sealed Product. Sneakers: Jordan, Nike, Adidas, New Balance, Asics, Other Brands. Collectibles: Coins & Currency, Comics, Toys & Figures, LEGO, Vinyl, Sports Memorabilia, Other Collectibles."

First observedOct 16, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real context: results are limited to *active* listings and the domain is strictly barter (no purchase path). It stops short of disclosing result ordering or default result volume, which are only implied by the output schema and limit parameter.

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?

Three sentences, front-loaded with the usage trigger, then behavior, then the domain constraint. The middle sentence enumerating return fields is largely redundant given an output schema exists, which is the only wasted space.

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 14-parameter search tool with full schema coverage, annotations, and an output schema, the description covers when to use it and the key domain constraint without needing to restate return values. Only pagination/ordering behavior is left entirely to the schema.

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 coverage is 100% with rich enum descriptions (including category/subcategory enumerations and per-category notes like sneaker sizing and card grading), so the schema carries parameter meaning. The description only summarizes the three main filter axes and adds no syntax or combination rules beyond it.

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?

States a specific verb and resource ('Searches active listings') plus the filter axes (text, category, type) and the returned fields, so the agent knows exactly what it gets. It does not explicitly contrast itself with the nearest siblings (list_my_listings, list_saved_listings, get_listing), leaving that differentiation to the agent.

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?

'Use this when the user wants to find goods or services offered for barter' gives a clear triggering condition. There are no explicit exclusions or named alternatives, so the agent must infer that browsing one's own or saved listings uses a different tool.

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

All TraydStar 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.