TraydStar

Create a listing

create_listing

Use this when the user wants to offer a good or service for barter on TraydStar. Publishes a public listing on their account and returns its id. Photos can't be attached here; the user can add them on the website. Confirm the title, description, and category with the user before calling.

Input Schema

Name	Required	Description
`kind`	No	offer (default) for something the user has; wanted for something the user is looking for, with want fields describing what they would give
`type`	Yes	GOOD for a physical item, SERVICE for work, BOTH if it includes both
`draft`	No	true saves it unpublished; publish later with set_listing_status
`ships`	No	The user will ship it (default false)
`title`	Yes	Short name of what is offered
`pickup`	No	Can be handed over in person (default true)
`details`	No	Only for Trading Cards and Sneakers listings: the facts collectors trade on. Use the card fields for Trading Cards and the sneaker fields for Sneakers.
`category`	Yes	The category it belongs in
`condition`	No	Condition, for physical goods
`want_tags`	No	Short tags for what the user wants in exchange
`description`	Yes	What is offered, in the user's words
`subcategory`	No	A subcategory of that category, if one applies. 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.
`location_city`	No	City shown on the listing
`stated_value_usd`	No	The user's own estimate of its value in US dollars, used to match fair trades
`want_description`	No	What the user would like in exchange

Output Schema

Name	Required	Description	Default
`listing_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 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 / details

Added value: +{
+  "additionalProperties": false,
+  "description": "Only for Trading Cards and Sneakers listings: the facts collectors trade on. Use the card fields for Trading Cards and the sneaker fields for Sneakers.",
+  "properties": {
+    "box": {
+      "description": "Sneakers: comes with the original box",
+      "type": "boolean"
+    },
+    "card_condition": {
+      "description": "Trading Cards: condition of a raw card",
+      "enum": [
+        "Near Mint",
+        "Lightly Played",
+        "Moderately Played",
+        "Heavily Played",
+        "Damaged"
+      ],
+      "type": "string"
+    },
+    "card_number": {
+      "description": "Trading Cards: number on the card, e.g. 4/102",
+      "maxLength": 20,
+      "type": "string"
+    },
+    "cert_number": {
+      "description": "Trading Cards: certification number on the slab label, so the other side can look it up",
+      "maxLength": 24,
+      "type": "string"
+    },
+    "colorway": {
+      "description": "Sneakers: colorway name",
+      "maxLength": 80,
+      "type": "string"
+    },
+    "grade": {
+      "description": "Trading Cards: grade on the slab, e.g. 10 or 9.5",
+      "maxLength": 12,
+      "type": "string"
+    },
+    "graded": {
+      "description": "Trading Cards: true for a slabbed card (then give grader and grade), false or omitted for raw",
+      "type": "boolean"
+    },
+    "grader": {
+      "description": "Trading Cards: grading company of a graded card",
+      "enum": [
+        "PSA",
+        "BGS",
+        "CGC",
+        "SGC",
+        "Other"
+      ],
+      "type": "string"
+    },
+    "model": {
+      "description": "Sneakers: model, e.g. Air Jordan 1 High OG",
+      "maxLength": 80,
+      "type": "string"
+    },
+    "receipt": {
+      "description": "Sneakers: comes with proof of purchase",
+      "type": "boolean"
+    },
+    "set": {
+      "description": "Trading Cards: set or series, e.g. Base Set, 2023 Topps Chrome",
+      "maxLength": 80,
+      "type": "string"
+    },
+    "size": {
+      "description": "Sneakers: US size, half sizes allowed (needs size_group)",
+      "maximum": 20,
+      "minimum": 1,
+      "type": "number"
+    },
+    "size_group": {
+      "description": "Sneakers: which US size run",
+      "enum": [
+        "Men's",
+        "Women's",
+        "Youth"
+      ],
+      "type": "string"
+    },
+    "sneaker_condition": {
+      "description": "Sneakers: condition",
+      "enum": [
+        "New with box",
+        "New without box",
+        "Worn once",
+        "Used"
+      ],
+      "type": "string"
+    },
+    "style_code": {
+      "description": "Sneakers: style code from the box or tag",
+      "maxLength": 20,
+      "type": "string"
+    },
+    "subject": {
+      "description": "Trading Cards: player or character",
+      "maxLength": 80,
+      "type": "string"
+    },
+    "variant": {
+      "description": "Trading Cards: holo, 1st edition, parallel, refractor and so on",
+      "maxLength": 80,
+      "type": "string"
+    },
+    "year": {
+      "description": "Trading Cards: year printed",
+      "maximum": 2100,
+      "minimum": 1860,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / subcategory / description

Previous value: -"A subcategory of that category, if one applies"New value: +"A subcategory of that category, if one applies. 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.8/5.0

Behavior3/5

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

Annotations already declare the non-destructive but write operation, so a lower bar applies. The description adds genuinely useful behavioral context – the listing is public, an id is returned, photos can't be attached and must be added on the website, and user confirmation is required before calling. It doesn't disclose what draft=true implies behaviorally (aside from the schema) or any validation/auth failure modes, so it's helpful but not rich.

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?

Three front-loaded sentences, each doing distinct work (trigger, side effect, constraint, precondition) with no repetition. Compact for a tool of this complexity.

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?

An output schema exists, so the id return value need not be explained, and the annotations cover safety. The description adds the public-visibility fact and photo constraint that an agent would otherwise miss. Minor gap: it doesn't say what happens if the user later wants to edit (update_listing) or publish a draft (set_listing_status), though the schema does mention set_listing_status.

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 detailed enum explanations and a nested details object for cards/sneakers, so the schema already documents all 15 params. The description adds only the confirmation requirement and photo exclusion, which are workflow semantics rather than parameter meaning. Baseline 3 is appropriate.

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: publishes a public barter listing on the user's account and returns its id. Clearly distinct from update_listing, remove_listing, and set_listing_status among siblings. Doesn't explicitly name a sibling alternative, which keeps it just under a 5.

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?

States the triggering condition ('when the user wants to offer a good or service for barter') and an important precondition (confirm title, description, category with the user first), plus the photos limitation. It doesn't say when to prefer draft=true or set_listing_status over creating directly, nor does it name update_listing as the alternative for editing.

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.