Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_get_oauth_url

Obtain an eBay OAuth authorization URL for user consent, initiating the OAuth 2.0 Authorization Code flow to grant API permissions.

Instructions

Generate the eBay OAuth authorization URL for user consent. The user should open this URL in a browser to grant permissions to the application. This supports the OAuth 2.0 Authorization Code grant flow. The redirect URI can be provided as a parameter or will be read from EBAY_REDIRECT_URI environment variable.

IMPORTANT: eBay has different OAuth scopes available for production vs sandbox environments:

  • Sandbox includes additional Buy API scopes (e.g., buy.order.readonly, buy.guest.order, buy.shopping.cart) and extended Identity scopes

  • Production includes sell.edelivery, commerce.message (explicit), and commerce.shipping scopes not available in sandbox

  • If you provide custom scopes, they will be validated against the current environment (set via EBAY_ENVIRONMENT). Any scopes not valid for the environment will generate warnings.

OAUTH FLOW INSTRUCTIONS:

  1. Generate OAuth URL with this tool (optionally specify scopes)

  2. User opens URL in browser, authorizes, and gets redirected with a code parameter

  3. Use ebay_exchange_authorization_code tool with the code (URL-encoded format accepted)

  4. Tokens are automatically stored and will auto-refresh every 2 hours

COMMON SCOPES:

TROUBLESHOOTING:

  • Authorization codes expire in ~5 minutes - get fresh code if "invalid grant" error

  • "Insufficient permissions" errors mean you need to re-authorize with additional scopes

  • OAuth URL format: Use + to separate scopes (e.g., scope=scope1+scope2), not %2B

  • Refresh tokens last 18 months and are saved to .env file for persistence

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoOptional state parameter for CSRF protection
scopesNoOptional array of OAuth scopes. If not provided, uses environment-specific default scopes (production or sandbox based on EBAY_ENVIRONMENT). Custom scopes will be validated against the environment.
redirectUriNoOptional redirect URI registered with your eBay application (RuName). If not provided, will use EBAY_REDIRECT_URI from .env file.
Behavior5/5

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

With no annotations, the description fully discloses the tool's behavior: it generates a URL requiring user browser authorization, supports OAuth 2.0 Code flow, validates scopes against environment, and explains auto-refresh of tokens. It also covers scope differences between sandbox/production.

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 comprehensive but slightly long due to sections on common scopes and troubleshooting. However, the first sentence captures the essence, and every section adds value. It is well-structured with clear headings.

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?

Despite no output schema and no annotations, the description fully covers the tool's purpose, parameters, environment-specific behavior, and complete OAuth flow. It includes practical details like scope validation and troubleshooting, making it self-contained.

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?

All 3 parameters (state, scopes, redirectUri) have schema descriptions, and the description adds significant context: state is for CSRF protection, scopes can be environment-specific defaults or custom, redirectUri defaults from env var. This goes well beyond the schema.

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 starts with 'Generate the eBay OAuth authorization URL for user consent,' clearly stating the verb and resource. It distinguishes this authentication tool from the many listing, selling, and management sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a step-by-step OAuth flow, explicitly stating when to use this tool (step 1) and when to use the sibling 'ebay_exchange_authorization_code' (step 3). It also includes troubleshooting scenarios like expired codes and insufficient permissions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jyarbro/ebay-seller-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server