eBay Sell

Getting a token — the Sell APIs need a user token, not an application token.

1. Register at developer.ebay.com and create a production keyset. Note the App ID (client id), Cert ID (client secret) and an RuName (redirect URI name).
2. Run the authorization-code grant once for the seller account, requesting the scopes you need: sell.inventory, sell.fulfillment, sell.account, optionally read-only variants. eBay's OAuth documentation has a browser-based token tool for this.
3. Keep the refresh token — it lasts around 18 months — and set EBAY_CLIENT_ID, EBAY_CLIENT_SECRET and EBAY_REFRESH_TOKEN. AnythingMCP mints access tokens from it (access tokens expire in two hours, which is why the refresh token is the thing to store).
4. Set EBAY_MARKETPLACE_ID to the marketplace the seller trades on, e.g. EBAY_DE, EBAY_US, EBAY_GB. eBay reads it from the X-EBAY-C-MARKETPLACE-ID header and answers differently per marketplace.

Sandbox is a separate host. This adapter points at api.ebay.com (production). The sandbox lives at api.sandbox.ebay.com with its own keyset and its own tokens; a production token there fails with a confusing 401.

Inventory vs Trading. The Sell Inventory API only sees listings created through it or migrated into it. A long-established seller whose listings were created with the legacy Trading API may find ebay_sell_list_inventory_items almost empty while their eBay shop is full — that is expected, and the migration is a one-time API call eBay documents.

Limits: most Sell endpoints allow a few thousand calls a day per application. Pace bulk work.

Writes: ebay_sell_update_offer_price changes a live listing's price, which buyers see immediately.