Skip to main content
Glama

search

Search eBay listings by keyword, category, price, condition, and sort order. Filter results by marketplace and host to find matching items.

Instructions

Search eBay items via the Browse API.

Args: query: keyword search string. Required. category_id: numeric eBay category ID to restrict the search. condition: one of NEW, LIKE_NEW, NEW_OTHER, USED_EXCELLENT, USED_VERY_GOOD, USED_GOOD, USED_ACCEPTABLE, FOR_PARTS_OR_NOT_WORKING, MANUFACTURER_REFURBISHED, CERTIFIED_REFURBISHED, or several other refurbished tiers. Case-sensitive. min_price: minimum item price (in currency). max_price: maximum item price (in currency). currency: ISO currency code for the price filter (default "USD"). sort: one of "best_match" (default), "price_asc", "price_desc", "newly_listed", "ending_soonest". limit: number of hits per page. Default 20, hard cap 200. offset: pagination offset. marketplace: eBay marketplace ID (default "EBAY_US"). Other examples: "EBAY_GB", "EBAY_DE", "EBAY_IT". host: which configured host to use ("sandbox" or "production"). If omitted, uses the config's default_host.

Returns: dict with: - host: which host was actually targeted - total: total matching items per eBay - limit, offset, next_offset (None when there's no next page) - hits: list of item summaries (item_id, title, price, currency, condition, seller, image_url, ends_at, buying_options, web_url, bid_count if applicable)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
category_idNo
conditionNo
min_priceNo
max_priceNo
currencyNoUSD
sortNobest_match
limitNo
offsetNo
marketplaceNoEBAY_US
hostNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries full burden. It discloses pagination behavior (limit, offset, next_offset), return structure, and default values. However, it does not mention rate limits, authentication requirements, or error handling.

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 well-structured with Args and Returns sections, front-loading the purpose. It is slightly lengthy but every sentence adds value. A minor improvement could be trimming redundancy.

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 the complexity of 11 parameters and no output schema, the description is comprehensive. It explains all parameters, return values, and defaults, covering everything an agent needs to invoke the tool correctly.

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?

Schema description coverage is 0%, but the description provides detailed semantics for all 11 parameters: required status, values for condition and sort, defaults, and examples like marketplace codes. This fully compensates for the lack of schema descriptions.

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 'Search eBay items via the Browse API', which is a specific verb+resource. It distinguishes from sibling tools like get_item and get_watchlist by focusing on searching across items.

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 searching items but provides no explicit guidance on when to use this tool versus alternatives like get_item or when not to use it. No exclusions or comparisons are given.

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

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