Un servidor MCP que permite a Claude (o a cualquier cliente MCP) buscar anuncios de eBay a través de la Browse API oficial.
Pide "find me a mechanical keyboard under $100, buy-it-now only, free shipping" y el asistente puede ir a buscarlo de verdad.
eBay results for "mechanical keyboard" — showing 3 of about 41,208 matches
1. Keychron K8 Pro Wireless Mechanical Keyboard - Brown Switches — $79.99
total $79.99 · free shipping · New · was $99.00 (19% off)
seller keeb_supply · 99.6% positive (8421 ratings) · top rated, ships from US
Item v1|335894120043|0 · https://www.ebay.com/itm/335894120043
2. Ducky One 3 TKL Mechanical Keyboard RGB Hot-Swappable — $84.50
total $92.45 · $7.95 shipping · New
seller pc_parts_direct · 98.9% positive (3310 ratings) · accepts offers
Item v1|326770118254|0 · https://www.ebay.com/itm/326770118254Cada herramienta es de solo lectura. Este servidor busca y lee anuncios. No puede pujar, añadir al carrito, hacer un pedido ni gastar dinero. Cuando quieras comprar, te entrega un enlace al anuncio y tú mismo finalizas la compra.
Está construido sobre la API oficial Browse API de eBay — sin scraping, sin automatización de navegador, sin reutilización de cookies. No se romperá ante un cambio de diseño ni te hará incumplir las condiciones de uso de eBay.
Related MCP server: ebay-browse-mcp
Herramienta | Para qué sirve |
| Búsqueda por palabras clave con filtros de precio, estado, formato de compra, envío y ubicación. |
| Registro completo de un anuncio: características del artículo, vendedor, devoluciones, hora de fin de subasta. |
| Solo anuncios con un descuento de al menos un N % sobre su precio original, primero los más baratos. |
| Muestra la configuración actual y hace una llamada de prueba en vivo. Ejecuta esto primero cuando algo no funcione. |
Dos cosas que conviene saber sobre search_ebay, porque son lo que eBay tiene y un catálogo de precio fijo no:
buying_option filtra por auction, buy_it_now o accepts_offers.
sort: "ending_soonest" — combinado con buying_option: "auction", así es como encuentras subastas que están a punto de cerrar.
Inicia sesión en developer.ebay.com/my/keys.
Crea una aplicación y abre el conjunto de claves de Production.
Copia el App ID (Client ID) y el Cert ID (Client Secret).
Eso es todo. Este servidor utiliza el flujo OAuth de credenciales de cliente, por lo que no necesitas un token de usuario, una URI de redirección ni un "RuName".
Las cuentas de desarrollador nuevas pueden tener que completar la verificación de eBay antes de que se abra la página de claves; normalmente tarda aproximadamente un día hábil.
git clone https://github.com/Kirat5690/shopping-mcp.gitcd shopping-mcp && npm install && npm run buildclaude mcp add shopping --env EBAY_CLIENT_ID=your-app-id --env EBAY_CLIENT_SECRET=your-cert-id -- node /absolute/path/to/shopping-mcp/dist/index.jsEdita claude_desktop_config.json:
macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
Windows — %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"shopping": {
"command": "node",
"args": ["C:\\path\\to\\shopping-mcp\\dist\\index.js"],
"env": {
"EBAY_CLIENT_ID": "your-app-id",
"EBAY_CLIENT_SECRET": "your-cert-id",
"EBAY_MARKETPLACE_ID": "EBAY_US"
}
}
}
}Reinicia el cliente y pídele que ejecute check_ebay_connection para confirmar que las credenciales funcionan.
Variable | Obligatoria | Por defecto | Notas |
| sí | — | App ID del conjunto de claves de producción. |
| sí | — | Cert ID del mismo conjunto de claves. |
| no |
|
|
| no |
| Configúralo en |
| no | — | Devuelve enlaces de anuncios con etiqueta de afiliado. |
| no | — | Mejora la precisión del coste de envío. |
| no | — | Código de país ISO, p. ej. |
| no |
| Tiempo de espera por solicitud. |
El precio final es lo que se ordena. La ordenación por precio utiliza el precio del artículo más el envío, de modo que un artículo barato con un envío caro no gana por una tecnicidad. La ordenación por precio de eBay no siempre hace esto.
Algunos anuncios no tienen total. Cuando eBay indica el envío como calculado al finalizar la compra, no hay precio final hasta que se conoce una dirección de entrega, y el anuncio lo indica en lugar de adivinar.
Sin conversión de divisas. Los precios se muestran en la moneda del propio marketplace, exactamente como los devuelve eBay.
Los anuncios son ventas individuales, no entradas de catálogo. Dos resultados con títulos casi idénticos pueden diferir en estado, contenido del lote o región. Merece la pena comprobarlo antes de tratarlos como el mismo artículo.
find_deals solo ve descuentos anunciados. Filtra por el precio tachado "was" de eBay, por lo que un anuncio realmente barato que nunca declaró un descuento no aparecerá.
npm testLa suite se ejecuta sin ninguna credencial de eBay. Cubre la lógica de los importes y del precio final, el formato de salida y una prueba de protocolo MCP de extremo a extremo que arranca el servidor a través de stdio y ejercita el registro de herramientas, la validación de esquemas y las rutas de credenciales no configuradas.
npm run watch # recompile on change
npm run typecheck # types only, no emitEstructura:
src/
index.ts server entry point and stdio wiring
tools.ts MCP tool definitions
ebay.ts Browse API client and OAuth token cache
config.ts environment parsing and marketplace table
money.ts price parsing, landed totals, ranking
format.ts human-readable output
http.ts fetch with timeout and retryLas versiones anteriores también admitían Amazon a través de la Product Advertising API. Eso se eliminó en la v0.2.0: la PA-API requiere una cuenta de Amazon Associates aprobada, y Amazon revoca el acceso si la cuenta no realiza ventas que cumplan los requisitos — un listón demasiado alto para que la mayoría de la gente consiga poner el servidor en marcha.
El cliente de Amazon y su firma AWS SigV4 se conservan en el historial de git en la etiqueta v0.1.0-amazon por si tienes una cuenta aprobada y quieres recuperarlos.
MIT — consulta LICENSE.
No está afiliado, respaldado ni patrocinado por eBay. Tu uso de la API de eBay se rige por el eBay API License Agreement.
Report how eBay is configured and make one live test call to confirm the credentials work. Run this first whenever a search fails or returns nothing.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds important behavioral context: 'make one live test call to confirm the credentials work.' This clarifies that despite being read-only, the tool performs an actual network call to the eBay API for testing, which is beyond the basic read-only label. It also implies credential validation, adding value over the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: two sentences, with the purpose front-loaded and the usage guidance immediately after. No wasted words, and it covers purpose, behavior, and usage in a compact form.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters and no output schema, the description fully covers what an agent needs to know: what it does (reports config, tests credentials), when to use it (after a failed search), and the side-effect (live call). It is complete for its simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters in the schema, so the baseline is 4. The description does not need to explain parameters since none exist. It adequately explains the tool's behavior without needing parameter-level detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Report how eBay is configured and make one live test call to confirm the credentials work.' This is a specific action (report/test) on a specific resource (eBay configuration), and it distinguishes itself from sibling tools like search_ebay and get_listing_details by focusing on connection/credential verification rather than data retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit when-to-use guidance: 'Run this first whenever a search fails or returns nothing.' This is a clear trigger condition that indicates precedence over sibling tools. However, it does not explicitly mention when not to use it or list alternative tools, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search eBay for listings currently discounted off their original price. Returns only items whose advertised saving meets the threshold, cheapest landed price first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many listings to scan before filtering (default 25). Raise this if nothing comes back. | |
| query | Yes | Product or category to hunt for deals in, e.g. 'mechanical keyboard'. | |
| condition | No | Item condition (default new). | |
| max_price | No | Ignore listings above this price. | |
| min_savings_percent | No | Minimum advertised discount off the original price (default 20). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds behavioral details: it filters by advertised savings threshold and sorts by landed price, which goes beyond the annotations. It does not describe pagination or response format, but with the annotations covering the basic side effects, this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two concise sentences: the first states the primary action, the second adds the filtering and ordering behavior. There is zero fluff, and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 5 parameters, no output schema, and helpful annotations, the description is sufficiently complete. It explains the core filtering and ordering behavior, which is the key differentiator. While it doesn't describe return fields or pagination, the simplicity of the tool and schema richness compensate. It could add more detail on the response structure, but it is not critically missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for all 5 parameters, each with its own description. The tool description does not add additional parameter-level clarification beyond what the schema provides, so the baseline of 3 is appropriate per the rubric.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Search' and the resource 'eBay listings' with a specific scope: discounted items meeting a savings threshold. It distinguishes itself from siblings like search_ebay by focusing on advertised discounts and cheapest landed price first, making its purpose unique.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use it (when seeking discounted items) via its focus on savings thresholds and ordering, but it does not explicitly mention alternatives or exclusions. The existence of sibling tools like search_ebay suggests a differentiation, but no direct comparison is made, so it's clear context without explicit when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Fetch the full record for one eBay listing: price, condition, availability, seller rating, item specifics, return policy, and auction end time. Accepts either the v1|...|0 item id or the legacy numeric id from an eBay URL.
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes | eBay item id — either 'v1|326012345678|0' or the numeric id from the listing URL. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows it's a safe read operation with external side effects. The description adds the specific data returned (price, condition, etc.) but doesn't discuss error behavior, latency, or rate limits. With annotations covering the safety profile, a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences: the first states the purpose with a clear list of fields, the second explains the parameter format. No fluff, front-loaded with the core function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a simple single-parameter tool with full schema coverage and safety annotations, the description is complete. It covers what data is returned, which is sufficient. No output schema exists, but the listed fields serve as a partial return description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema description already explains the item_id formats fully (100% coverage). The tool description reinforces that it accepts either format but adds no new meaning beyond the schema. Baseline 3 is correct.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches full details for one eBay listing, enumerating specific data fields (price, condition, availability, seller rating, etc.). It distinguishes from siblings (search_ebay, find_deals) by focusing on a single item rather than searching or finding deals.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when you need full details for a specific listing, as opposed to search or deals tools. It does not explicitly say when NOT to use it or name alternatives, but the context is clear given the sibling names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search eBay for listings matching a keyword query, with optional price, condition, buying-format, and shipping filters. Returns title, price, shipping, landed total, seller rating, and a link for each listing. Read-only: this never bids, adds to a cart, or places an order.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Result ordering (default relevance). 'ending_soonest' is most useful combined with buying_option='auction' to find auctions about to close. | |
| limit | No | How many listings to return (default 10). | |
| query | Yes | What to search for, e.g. 'Sony WH-1000XM5 headphones'. | |
| condition | No | Item condition (default any). | |
| max_price | No | Maximum price, in the marketplace's own currency. | |
| min_price | No | Minimum price, in the marketplace's own currency. | |
| buying_option | No | Buying format (default any). Use 'auction' for bidding, 'buy_it_now' for fixed price. | |
| seller_location | No | Two-letter country code to restrict where items ship from, e.g. 'US' or 'CA'. | |
| free_shipping_only | No | Only return listings that ship free. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value beyond annotations: it explicitly states 'Read-only: this never bids, adds to a cart, or places an order,' which is more specific than the generic readOnlyHint annotation. It also discloses the output fields (title, price, shipping, etc.), which is a behavioral trait not covered by annotations or schema. No contradiction; this enhances transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences: the first states the core action and filters, the second clarifies read-only behavior. It is front-loaded with the key information and contains zero fluff. Every word serves a purpose, making it highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 9 parameters, but the schema fully documents them, and the description explains what the tool returns and its read-only nature. It lacks mention of pagination or how to interpret structured results, but given the schema coverage and the read-only clarification, the description is complete enough for an agent to invoke correctly. The openWorldHint is not elaborated, but that's acceptable since it's a hint rather than a requirement.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so each parameter has detailed descriptions. The tool description itself only gives a high-level overview ('optional price, condition, buying-format, and shipping filters'), adding marginal value beyond the schema. However, it does connect the filters to the search intent, which aligns with the baseline of 3. No specific parameter semantics beyond what schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is specific and action-oriented: 'Search eBay for listings matching a keyword query' with optional filters and a clear list of returned fields (title, price, shipping, landed total, seller rating, link). It distinguishes from siblings by focusing on search behavior, and the read-only note further clarifies scope. The verb-resource pair is unambiguous and distinct from check_ebay_connection, get_listing_details, and find_deals.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides some usage context (search for listings, optional filters) but does not explicitly tell when to use this tool over siblings like get_listing_details or find_deals. It also includes a helpful tip in the schema about using 'ending_soonest' with auctions, but that guidance is embedded in the schema description, not the main description. No clear when-not or alternative tool mention, so it is adequate but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.2.0check_ebay_connectionfind_dealsget_listing_detailssearch_ebayScored across 4 tools
Most tools are clearly distinct: check_ebay_connection, search_ebay, get_listing_details each target different actions. search_ebay and find_deals have some overlap, but find_deals is specifically for discounted listings with a savings threshold, so the boundary is clear enough.
Tool names follow a readable snake_case verb_noun pattern: check_ebay_connection, search_ebay, get_listing_details, find_deals. The only minor inconsistency is using both 'search' and 'find' for similar retrieval actions, but the pattern remains predictable.
Four tools is on the small side but appropriate for a focused eBay look-up server. The surface is tight and avoids unnecessary endpoints, though it is slightly minimal for a general 'shopping' MCP.
The tool set covers the core read-only shopping workflow: connectivity verification, keyword search, deal discovery, and listing details. It intentionally omits purchase actions, and while category browsing or seller info could be added, the current surface is not severely incomplete.
Read-only product discovery, merchant trust, shipping and returns for SVV-Schatzoekers.
Live search across 250,000+ verified UK and Canada retail deals. Read-only, no auth required.
Search and browse global classifieds across 80 markets. No auth required for read-only access.
eBay MCP — Browse + Taxonomy APIs via client_credentials OAuth
