Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_revise_listing

Update an existing eBay listing's quantity, price, title, or other fields. Send only the fields to change with the item ID to apply the revision.

Instructions

Revise an existing listing. Update quantity, price, title, description, or any other field.

Uses the Trading API: ReviseFixedPriceItem for format FIXED_PRICE (default) and ReviseItem for format AUCTION (check ListingType with ebay_get_listing when unsure; eBay limits auction revisions once bids exist). Only send the fields you want to change.

Examples:

  • Update quantity: { "Quantity": 10 }

  • Update price: { "StartPrice": 14.99 }

  • Update title: { "Title": "New Title" }

  • Raise an auction reserve: { "format": "AUCTION", "fields": { "ReservePrice": 30 } }

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
fieldsYesTrading API Item fields to update
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 revise

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 / fields / description
      Previous value: -"Fields to update (e.g., { \"Quantity\": 10, \"StartPrice\": 14.99 })"New value: +"Trading API Item fields to update"
  3. First observedv1.8.10

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the minimal readOnlyHint=false annotation. It discloses that different Trading API calls are used per format, that mixed-format payloads are rejected before any eBay request, that auction revisions are constrained once bids exist, and that a user OAuth token is required. These are meaningful behavioral details an agent needs to invoke the tool safely.

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 long, but nearly every sentence carries critical constraints, examples, or field semantics. The purpose is front-loaded, and the examples are compact and varied. It is not as lean as the ideal, but the complexity of the Trading API format rules justifies the length.

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?

Given that there is no output schema and only sparse annotations, the description covers the essential invocation context: required auth, format default, allowed fields, and format-specific safeguards. It does not describe the response shape or common error conditions, but the core usage and constraints are sufficiently complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only says 'fields' is a Trading API Item fields object, but the description adds extensive semantics: example payloads for Quantity, StartPrice, Title, and ReservePrice, plus format-specific rules for ListingDuration, Quantity, BuyItNowPrice, and Best Offer. This strongly compensates for the open-ended additionalProperties schema and clarifies how to structure a valid request.

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 clear verb and object: 'Revise an existing listing.' It lists concrete updatable fields (quantity, price, title, description) and explains that it uses ReviseFixedPriceItem for FIXED_PRICE and ReviseItem for AUCTION, which distinguishes it from create/end/relist siblings. The purpose is unambiguous and connected to both the tool name and the domain.

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 gives actionable guidance: send only changed fields, choose format via the format parameter or default to FIXED_PRICE, and check ListingType with ebay_get_listing when unsure. It also warns that auction revisions are limited once bids exist. It does not explicitly mention when to prefer create_listing or end_listing, but the 'existing listing' framing makes 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