Skip to main content
Glama
jnslmk

ebay-mcp

by jnslmk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EBAY_ENVNosandbox or productionsandbox
MCP_HOSTNoHTTP bind host0.0.0.0
MCP_PATHNoHTTP path/mcp
MCP_PORTNoHTTP bind port8000
MCP_TRANSPORTNohttp (streamable-HTTP) or stdiohttp
EBAY_CLIENT_IDYesApp ID (Client ID) from your eBay Developer keyset.
EBAY_MARKETPLACENoMarketplace: EBAY_DE, EBAY_US, EBAY_GB, ...EBAY_DE
EBAY_CLIENT_SECRETYesCert ID (Client Secret) from your eBay Developer keyset.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_ebayA

Search eBay listings by keyword, with optional filters and sorting.

query is a strict AND over 2-4 short keywords matched against the listing TITLE only (see the query field's description) — a zero-result response carries a hint explaining why instead of a bare empty list, and one automatic narrowed retry may already have run (see fallback_query). Returns listing summaries — id, title, price, condition, seller reputation, location, thumbnail and URL. Pass an item's item_id to get_item_details for the full record. Prices and currency follow the configured marketplace. min_price/max_price are a convenience over filter_expr's price range syntax — see those parameters' own descriptions for the rule against combining the two.

get_item_detailsA

Retrieve the shaped detail record for a single eBay item.

Use after search_ebay surfaces something worth a closer look: full description, item specifics (aspects), all images, shipping options, return policy, seller and location.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: search_ebay discovers listings, while get_item_details retrieves full details for a specific item. No overlap or ambiguity in their roles.

Naming Consistency5/5

Both names follow a consistent verb_noun pattern with snake_case (search_ebay, get_item_details), making them predictable and readable.

Tool Count3/5

With only 2 tools, the server feels thin for a domain as broad as eBay, but the two tools cover a basic search-and-detail workflow without redundancy.

Completeness3/5

The surface covers search and retrieval of item details, sufficient for a browsing use case, but lacks advanced features like pagination, seller-specific queries, or listing operations. There are notable gaps for more complex workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources