Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_create_listing

Create a new eBay listing as a fixed-price item or auction. Specify complete item details; the tool applies format-specific rules for duration, pricing, reserve, and buy-it-now options.

Instructions

Create a new fixed-price listing or auction.

Uses the Trading API: AddFixedPriceItem for format FIXED_PRICE (default) and AddItem with ListingType Chinese for format AUCTION. Requires complete item details.

AUCTION items take StartPrice as the opening bid, a day-count ListingDuration (Days_1/3/5/7/10; never GTC), Quantity 1, an optional ReservePrice above the opening bid, an optional BuyItNowPrice at least 30% above it, and Best Offer only without a BuyItNowPrice. FIXED_PRICE items take StartPrice as the price and ListingDuration GTC (the only fixed-price duration eBay accepts), and cannot carry ReservePrice or BuyItNowPrice. Payloads that mix the two formats are rejected before any eBay request. Reserve prices carry an eBay fee.

Required: User OAuth token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYesTrading API Item payload. FIXED_PRICE: StartPrice is the listing price and ListingDuration is GTC. AUCTION: StartPrice is the opening bid, ListingDuration is a day count (Days_1/3/5/7/10), Quantity is 1, an optional ReservePrice must exceed StartPrice, an optional BuyItNowPrice must be at least 30% above it (and excludes Best Offer); ListingType Chinese is added for you.
formatNoListing format, defaulting to FIXED_PRICE. AUCTION switches to the auction-capable Trading calls (AddItem, ReviseItem, EndItem, RelistItem) and enforces the auction Item rules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.16.0
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Listing format, defaulting to FIXED_PRICE. AUCTION switches to the auction-capable Trading calls (AddItem, ReviseItem, EndItem, RelistItem) and enforces the auction Item rules.",
+  "enum": [
+    "AUCTION",
+    "FIXED_PRICE"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / item / description
      Previous value: -"Trading API Item payload for AddFixedPriceItem"New value: +"Trading API Item payload. FIXED_PRICE: StartPrice is the listing price and ListingDuration is GTC. AUCTION: StartPrice is the opening bid, ListingDuration is a day count (Days_1/3/5/7/10), Quantity is 1, an optional ReservePrice must exceed StartPrice, an optional BuyItNowPrice must be at least 30% above it (and excludes Best Offer); ListingType Chinese is added for you."
  2. Changed1 schema field changedv1.14.1
    • changedInput schema / properties / item / description
      Previous value: -"Item details object. Required fields: Title, PrimaryCategory.CategoryID, StartPrice, ConditionID, Country, Currency, DispatchTimeMax, ListingDuration, ListingType (\"FixedPriceItem\"), Quantity, SKU."New value: +"Trading API Item payload for AddFixedPriceItem"
  3. First observedv1.8.10

TDQS

A4.3/5.0
Behavior5/5

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

The description goes well beyond the readOnlyHint=false annotation by naming the underlying Trading API calls, stating that mixed-format payloads are rejected before any eBay request, mentioning reserve price fees, and requiring a User OAuth token. No contradiction with annotations exists.

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?

The description is dense and well-organized, front-loading the core purpose before format-specific details and auth requirements. It is somewhat long, but every sentence earns its place given the complexity of listing creation.

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 complex nested-payload tool, the description covers auth, validation, format differences, fees, and the need for complete item details. It does not describe response or error behavior, but no output schema exists and the creation outcome is clearly implied.

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%, and both parameters already have detailed descriptions in the schema. The tool description largely restates the same item rules, though it adds useful context about fees, cross-format rejection, and auth. Because the schema carries the load, the description's added parameter value is modest.

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?

The description states a specific verb and resource: 'Create a new fixed-price listing or auction.' It clearly identifies the two supported formats and distinguishes this from sibling tools like ebay_revise_listing, ebay_end_listing, and ebay_get_listing by focusing on creation.

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?

It provides clear context for when to use this tool: creating new listings, with detailed format-specific rules about which payload fields apply. It does not explicitly name sibling alternatives or state when not to use it, but the creation scope and format guidance make the intended use clear.

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