Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_end_listing

Destructive

End any active eBay listing by item ID. Choose the listing format and an ending reason to stop it from selling.

Instructions

End/remove an active listing.

Uses the Trading API: EndFixedPriceItem for format FIXED_PRICE (default) and EndItem for format AUCTION. SellToHighBidder is only valid for auctions with bids.

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 end
reasonNoTrading API ending reason, defaulting to NotAvailable. SellToHighBidder only applies to AUCTION listings with bids.

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 / reason / description
      Previous value: -"Trading API ending reason, defaulting to NotAvailable"New value: +"Trading API ending reason, defaulting to NotAvailable. SellToHighBidder only applies to AUCTION listings with bids."
  2. Changed1 schema field changedv1.14.1
    • changedInput schema / properties / reason / description
      Previous value: -"Reason for ending (default: NotAvailable)"New value: +"Trading API ending reason, defaulting to NotAvailable"
  3. First observedv1.8.10

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark this as destructive, and the description adds useful non-obvious behavior: it selects EndFixedPriceItem for FIXED_PRICE and EndItem for AUCTION, restricts SellToHighBidder to auctions with bids, and requires a User OAuth token. This goes beyond the annotations without contradicting them.

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 short sentences, with the purpose front-loaded and each subsequent sentence earning its place by adding API routing, auction-only constraint, or the auth prerequisite. No filler or repetition beyond necessary emphasis.

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 3-parameter destructive action with fully described schema and destructive annotation, the description supplies the missing invocation context: required auth and which underlying API call applies to each format. It does not describe return values, but no output schema exists and the essential call conditions are covered.

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 description coverage is 100% and the schema already documents defaults, enums, and the SellToHighBidder restriction. The description repeats the format/reason behavior rather than adding new parameter meaning.

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?

Opens with 'End/remove an active listing,' which names a specific action and resource, and reinforces it by naming the Trading API calls (EndFixedPriceItem/EndItem). This clearly separates it from sibling tools like ebay_end_campaign or ebay_withdraw_offer.

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 'active listing' scope and the format-specific note (FIXED_PRICE vs AUCTION) give clear context for when to call it, and the auth requirement is stated. It does not explicitly name alternative maintenance tools such as ebay_revise_listing or ebay_relist_item, so it stops short of full when-not guidance.

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