mcp-ebay

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation5/5
Each tool has a clearly distinct purpose: searching, viewing details, tracking bids, placing bids, buying, viewing orders, and tracking shipments. No overlapping responsibilities confuse an agent's selection.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., search_products, place_bid, track_shipment). Minor pluralization differences (track_bids vs place_bid) do not break the pattern.
Tool Count5/5
With 7 tools, the set is well-scoped for an eBay buyer-centric server. Each tool covers a distinct aspect of the buying workflow—search, item details, bidding, purchasing, order history, and shipment tracking—without bloat.
Completeness4/5
The tool surface covers core buyer workflows: searching, inspecting items, bidding, buying, viewing orders, and tracking shipments. Minor gaps like canceling orders or leaving feedback are not critical for most use cases but prevent a perfect score.
Average 3.7/5 across 7 of 7 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 1 commit in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosing behavioral traits. It only notes the credential requirement, but omits critical details such as the bid being binding, potential fees, success/failure handling, or the effect on the user's account.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that immediately states the purpose and a key requirement. There is no wasted verbiage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a financially significant mutation tool with no annotations or output schema. The description is far too sparse: it fails to mention binding obligations, possible outcomes, error behavior, or what the response will look like. Significant context is missing for an AI agent to safely invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers 100% of parameters with descriptions, providing a baseline of 3. The description adds a small note about credentials, reinforcing the username/password fields, but does not materially enrich understanding of the bid_amount or item_id beyond what the schema already states.
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 clearly states the tool's action with a specific verb ('Place') and resource ('a bid on an eBay auction item'). It distinguishes itself from sibling tools like buy_it_now by focusing on auction bidding.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like buy_it_now. It only states that eBay credentials are required, but does not mention when placing a bid is appropriate or when other tools should be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only describes the search action and filters, but does not mention that the operation is read-only, whether authentication is required, rate limits, pagination behavior, or what the return response looks like. For a search tool, these are important behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that clearly communicates the core purpose. There is no redundant information, and it is front-loaded with the main action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While the schema fully documents parameters, the description lacks any information about the response format (e.g., list of items) or behavior like default result limits. Since there is no output schema, the description should compensate by explaining what the tool returns, but it does not.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all parameters are already documented in the schema. The description summarizes filters for price, condition, and sort order, which aligns with the schema but adds no additional meaning. It also omits mention of max_results, though the schema covers it.
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 uses the imperative 'Search' with a specific resource 'eBay products' and lists optional filters, making the tool's purpose immediately clear. It is distinct from sibling tools like place_bid, get_item_details, and track_shipment, which serve different actions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description states it is for searching eBay by keyword with filters, implying use when finding products. It does not explicitly name alternatives or exclusions, but the sibling context makes the use case clear. However, it lacks explicit guidance on when not to use it (e.g., when needing item details, get_item_details would be appropriate).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The verb 'View' implies a non-mutating operation, but with no annotations, the description carries the full burden of behavioral disclosure. It does not explain whether the response includes live data, pagination, or what 'status' entails (e.g., winning/outbid). Still, the read-only nature is reasonably conveyed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. Every word contributes to the core purpose, making it highly efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with no output schema, the description is nearly complete. It states the purpose clearly and implies a read-only operation. Minor gaps include not specifying what 'status' covers or whether the history includes current and past bids, but these are not critical for basic invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already has 100% coverage with a clear description for item_id ('eBay auction item ID'). The tool description adds no further parameter detail, so it meets the baseline without adding extra value 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 uses a specific verb ('View') and clearly identifies the resource ('bid history and status') and scope ('eBay auction item'). It is easily distinguishable from sibling tools such as place_bid (action) and get_item_details (item details), which focus on different aspects.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention that it is read-only or suggest it for tracking bid activity before placing a bid. There is no explicit 'when-not-to-use' or comparison with sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only lookup but does not explicitly state that it is non-destructive, what information is returned, or that authentication is required for item-based lookup beyond what the schema already mentions. This is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that fronts the primary verb and resource. Every word contributes to meaning, with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and four parameters, the description is too minimal. It fails to mention return format, authentication requirements for the item_id path (only in schema), or any error/edge cases. The tool's dual-mode behavior is described, but important contextual details are missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the description adds a small amount of context by clarifying that tracking_number and item_id represent two alternative lookup modes. However, it does not explain the syntax or relationships beyond what the schema already provides, so the baseline of 3 is appropriate.
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 clearly states the tool's function: 'Track a shipment by tracking number, or look up tracking for a specific item from your order history.' It uses a specific verb ('track') and identifies the resource (shipment), and distinguishes from siblings like track_bids by focusing on shipment tracking.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use the tool: when you have a tracking number or want to track an item from order history. It does not explicitly name alternatives or exclusion criteria, but the two usage modes make the intended scenarios obvious relative to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses a key behavioral trait: 'Proceeds to checkout — final payment must be completed on eBay.' This goes beyond the schema by explaining the workflow and that payment is not handled by the tool. However, it does not mention potential side effects like an irreversible purchase, authentication requirements beyond the passed credentials, or error conditions. With no annotations, more transparency could be provided.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and efficient, consisting of two sentences. The first sentence states the primary action, and the second clarifies the checkout flow. There is no redundant information or awkward phrasing, and the key details are front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the core action and the checkout handoff, but it lacks details on expected return values, success/failure behavior, or prerequisites (e.g., item must have Buy It Now available). Given that there is no output schema, the agent is left without guidance on what the tool returns. This gap makes the description incomplete for a transactional tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage of parameter descriptions, so the baseline is 3. The description adds no additional explanation of parameters such as quantity or username, relying entirely on the schema. It doesn't clarify how credentials are used or what quantity default means 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 clearly states the tool's function: 'Purchase an eBay item immediately using Buy It Now.' It specifies the verb, resource, and method, distinguishing it from sibling tools like place_bid which would be for auctions. The additional note about proceeding to checkout further clarifies the purchase flow.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for immediate purchases via Buy It Now, but it does not explicitly mention when not to use it or provide alternatives. Siblings like place_bid exist, but there is no direct comparison or exclusion statement, leaving the agent to infer the distinction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It explicitly notes 'Requires eBay credentials,' which is an important authentication requirement. The verb 'view' implies read-only behavior, but the description does not discuss side effects, output format, or security implications. This is moderate transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loaded with the primary purpose. Every word earns its place, with no fluff or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description should convey what the tool returns. 'Purchase history' implies a list of past orders, but the description does not specify the response structure, the effect of the 'days' parameter, or any error conditions. It is minimally adequate for a familiar concept but lacks completeness for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the input schema already describes username, password, and days. The description reinforces the credential requirement but does not add meaning beyond the schema. No additional parameter semantics are provided.
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 uses a specific verb and resource: 'View your eBay purchase history.' This clearly differentiates it from sibling tools like search_products, get_item_details, track_bids, place_bid, buy_it_now, and track_shipment, which all serve distinct purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description states the clear context: view your purchase history. It implies when to use it (when you need past orders) but does not explicitly exclude alternatives or mention when not to use it. The credential requirement provides an additional cue, but no direct comparison to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It implies a read-only operation ('get') and lists included detail fields, which adds some transparency. However, it does not disclose error handling (e.g., invalid/nonexistent item), rate limits, or permission requirements, leaving gaps for a tool with no annotation support.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the action (get), specifies the target (full details for an eBay item), and lists key content areas. Every phrase is informative with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema), the description covers the essential purpose and included details. It could optionally mention error cases or required authentication, but for a read-only detail fetcher, it is sufficiently complete for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single parameter item_id, which already describes it as an eBay item ID (numeric string). The description's 'by its item ID' adds no new meaning beyond the schema, so it meets the baseline for high schema coverage.
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 clearly states the tool's function: retrieving full details for an eBay item via its item ID, and it enumerates the types of details (price, condition, seller info, specs). This is a specific verb+resource form that effectively distinguishes it from sibling tools like search_products or place_bid.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage: when you have an item ID and need comprehensive details for that specific item. It provides clear context without explicitly naming alternatives or exclusivity, but the need for an item ID inherently differentiates it from search-oriented tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![mcp-ebay MCP server](https://glama.ai/mcp/servers/markswendsen-code/mcp-ebay/badges/card.svg)](https://glama.ai/mcp/servers/markswendsen-code/mcp-ebay)

Score Badge

Copy to your README.md:

[![mcp-ebay MCP server](https://glama.ai/mcp/servers/markswendsen-code/mcp-ebay/badges/score.svg)](https://glama.ai/mcp/servers/markswendsen-code/mcp-ebay)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/markswendsen-code/mcp-ebay'

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