eBay MCP Server

eBay

eBay sellers run orders, inventory SKUs, offers (live listings), account metrics, payout events, and catalog research from Seller Hub workflows.

First moves

1. Orders — recent fulfillment orders with line items, buyer addresses, and shipment status.
2. Inventory SKUs — catalog rows with product aspects, quantities, and condition details.
3. Offers — live listing offers tied to SKUs on a marketplace (US, UK, etc.).
4. Seller standards — program-level performance profile for the connected marketplace.
5. Customer service metrics — item-not-received and item-not-as-described benchmarks vs peers.
6. Financial events — payout-related transactions with optional date and type filters.
7. Catalog search — keyword or GTIN lookup when researching comps before listing.
8. Traffic report — impression and click metrics for listings over a date range.

Data model

Inventory SKU → offer → live listing. Orders reference line items with SKUs and legacy item ids. Financial events roll up to payouts separately from order ids.

Operational order

1. Start order triage for fulfillment questions — list recent orders before opening one by id.
2. For listing health, pair inventory SKUs with their live offers on the marketplace the user names.
3. Use catalog search for market-wide comps; inventory reads only cover the connected seller account.
4. Pull seller standards and customer service metrics when the user asks about account health or defect rates.
5. Use financial events for payout reconciliation — filter by date window to match the user's period language.

Writes

Create inventory SKUs and offers, then publish before expecting live quantity on site. Mark orders shipped with carrier and tracking on the fulfillment order id. Issue refunds and withdraw live offers only after explicit user approval. Promoted Listings campaigns need a funding strategy and marketing access.

Gotchas

• Marketplace matters — US, UK, and other sites use different marketplace ids; confirm the site when listing or reading offers.
• SKU before offer — live listings bind to inventory SKUs; create or update the SKU shell before publishing an offer.
• Orders vs payouts — order fulfillment status and financial payout events are separate views; do not conflate order ids with payout line items.
• Catalog search — keyword, category, or GTIN is required; results reflect the marketplace you target.
• Traffic reports — wide date ranges on large catalogs can be slow; narrow the window to the period the user named.
• Pagination — order, inventory, and finance lists paginate; follow next-page links when the user asks for more rows.
• Destructive seller actions — refunds and offer withdrawals need confirm_write after explicit approval.