Skip to main content
Glama

Search eBay

search_ebay
Read-onlyIdempotent

Searches eBay listings by keyword on one eBay site (domain, default com) and returns up to 20 listings from the first results page (title, url, price, condition, shipping, seller, items_sold). It does not read a single item page, bids or sold-price history; for one item, the REST endpoint /v1/ebay takes an item URL. For prices at other stores use google_shopping_prices. Required: query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_ebay"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesListing search text, 1-500 characters, e.g. "mechanical keyboard".
domainNoeBay site as its domain suffix: com, co.uk, de, it, fr, es, ca or com.au, e.g. "co.uk" for ebay.co.uk. Default com.com
resultsNoMaximum listings returned, integer 1-20, default 10, e.g. 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"eBay site: com, co.uk, de, it, fr, es, ca or com.au."New value: +"eBay site as its domain suffix: com, co.uk, de, it, fr, es, ca or com.au, e.g. \"co.uk\" for ebay.co.uk. Default com."
    • changedInput schema / properties / query / description
      Previous value: -"Product search query."New value: +"Listing search text, 1-500 characters, e.g. \"mechanical keyboard\"."
    • changedInput schema / properties / results / description
      Previous value: -"Maximum number of eBay listings to return."New value: +"Maximum listings returned, integer 1-20, default 10, e.g. 5."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds valuable behavioral context: it returns only the first results page, caps at 20 listings, lists the returned fields, and states it does not read item pages, bids, or sold-price history.

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 compact and front-loaded: purpose, scope/return fields, exclusions and alternatives, then required parameter. Every sentence contributes useful selection or invocation guidance.

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?

Given that no output schema exists, the description helpfully lists the returned listing fields and clarifies first-page-only behavior. Combined with annotations and full schema coverage, it gives enough context for an agent to call the tool 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%, so the schema already fully documents query, domain, and results parameters. The description repeats the required query and mentions the default domain and 20-result cap, but adds no syntax or filtering details 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 states a specific verb and resource: searches eBay listings by keyword on one eBay site. It also defines the return scope (up to 20 listings from the first results page) and distinguishes this from single-item lookup and other-store price search.

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?

It explicitly routes the agent away from this tool when a single item page is needed and when prices from other stores are needed, naming google_shopping_prices as the alternative. The required parameter is also stated, leaving little ambiguity about when to use this search.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources