Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_relist_item

Relist an ended eBay listing with optional price, duration, or format changes. Supports auction and fixed-price listings using the Trading API.

Instructions

Relist an ended listing, optionally with modifications.

Uses the Trading API: RelistFixedPriceItem for format FIXED_PRICE (default) and RelistItem for format AUCTION.

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.

Required: User OAuth token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoListing format, defaulting to FIXED_PRICE. AUCTION switches to the auction-capable Trading calls (AddItem, ReviseItem, EndItem, RelistItem) and enforces the auction Item rules.
itemIdYesThe eBay item ID to relist
modificationsNoOptional Trading API Item fields to change while relisting

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
+}
  2. Changed1 schema field changedv1.14.1
    • changedInput schema / properties / modifications / description
      Previous value: -"Optional fields to change when relisting (e.g., { \"Quantity\": 20 })"New value: +"Optional Trading API Item fields to change while relisting"
  3. First observedv1.8.10

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only provide readOnlyHint:false, so the description carries the full burden of behavioral disclosure. It goes well beyond that by explaining the internal API selection per format, the specific constraints (e.g., AUCTION Quantity=1, FIXED_PRICE only GTC, ReservePrice/BuyItNowPrice restrictions), and the pre-request rejection of mixed-format payloads. It also states the required OAuth token. This is rich behavioral transparency.

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?

The description is detailed but every sentence is purposeful. It leads with the core action, then efficiently covers the API routing and format-specific rules, ending with the OAuth requirement. There is no filler or redundancy. The structure makes it easy to scan and understand the key constraints.

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?

Given the tool's complexity—two distinct formats with different rules, a rejection path, and an optional modifications object—the description is exceptionally complete. It covers all necessary details for correct invocation, including the OAuth token, format constraints, and the default format. With no output schema, it does not need to describe return values. Nothing essential for an agent to call this tool correctly is missing.

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?

The input schema has 100% coverage with descriptions for all three parameters, so the baseline is 3. The description adds significant value by explaining how the 'format' parameter changes behavior (AUCTION vs FIXED_PRICE) and what fields each format accepts. However, it does not elaborate on the 'modifications' object beyond what the schema says, leaving that partially open. Overall, the added semantics for format are crucial and elevate it above baseline.

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 opens with a precise verb+resource: 'Relist an ended listing, optionally with modifications.' This clearly distinguishes it from siblings like ebay_create_listing, ebay_revise_listing, and ebay_end_listing. The mention of the underlying Trading API calls (RelistFixedPriceItem, RelistItem) reinforces the specific purpose.

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?

The description explicitly states the tool is for relisting ended listings, which is the primary usage context. It does not name alternative tools or explicitly say 'use this instead of X', but the scope is unambiguous. The format-specific rules further guide when each internal API path applies, though they don't address exclusions (e.g., 'do not use for active listings').

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