Skip to main content
Glama

ebay_find_active_items

Read-only

Search active eBay listings marketplace-wide with keyword filters for price, condition, category, and buying option. Paginate and sort results for precise item discovery.

Instructions

Search active eBay listings marketplace-wide (not the seller's own inventory). Uses the Buy Browse API item_summary/search with the application access token eBay requires for Browse, minted from client credentials under the basic api_scope. Supports pagination (limit/offset), sort (price, -price, newlyListed, endingSoonest), category restriction, and condition/buying-option/price filters plus a raw Browse filter passthrough. eBay documents that a search without a buying-option filter returns only listings that still offer FIXED_PRICE, so pass buyingOptions: ["AUCTION"] (or ["AUCTION", "FIXED_PRICE"] for both) to be sure of reaching auctions that have taken a bid. Returns cleaned summaries: itemId (feed into ebay_get_item_details), title, price (an auction's current bid when there is no fixed price, with bidCount), condition, buyingOptions, seller and feedback, first advertised shipping cost, auction end date, and listing URL. hasNext is the authoritative pagination signal, derived from the next link in eBay's paged-collection response: page forward by advancing offset in whole limit-sized steps while hasNext is true, and stop as soon as it is false. Neither total nor a short page is a pagination signal — total is eBay's match count for the query and in live testing came back as 0 once offset ran past the available result window, and a page can hold fewer items than limit without being the last one. The active-listing counterpart of ebay_find_completed_items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: "price" (asc, price+shipping), "-price" (desc), "newlyListed", or "endingSoonest". Omit for best-match relevance.
limitNoMaximum items to return (1–200). Defaults to 20.
queryYesSearch keywords for active listings (e.g. "iphone 14 pro 256")
filterNoRaw Browse filter expression appended to the generated filters for advanced cases (e.g. "sellers:{user1|user2}").
offsetNoZero-based result offset for pagination. Must be zero or a multiple of limit (eBay pages in whole limit-sized steps). Defaults to 0.
priceMaxNoMaximum price (inclusive).
priceMinNoMinimum price (inclusive).
conditionsNoCondition filters, e.g. ["NEW"], ["USED"], ["CERTIFIED_REFURBISHED"].
categoryIdsNoComma-separated eBay category ids to restrict the search (e.g. "9355").
buyingOptionsNoBuying option filters, e.g. ["FIXED_PRICE"], ["AUCTION"], ["BEST_OFFER"]. eBay documents that a search without this filter returns only listings that still offer FIXED_PRICE, and an auction loses that option once it takes a qualifying bid, so pass ["AUCTION"] (or ["AUCTION", "FIXED_PRICE"] for both) to be sure of reaching auctions.
priceCurrencyNoCurrency for priceMin/priceMax as a 3-letter code (e.g. "USD", "EUR"). Defaults to USD when a bound is set. eBay converts across currencies, but silently drops the entire price filter when the code is not one it recognises: an unsupported code returns unfiltered results rather than an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by detailing the underlying Browse API and token requirements, the auction/buying-option quirk, authoritative pagination via hasNext, the unreliability of total as a pagination signal, and the exact summary fields returned. This is substantial behavioral context that annotations alone do not provide.

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 long but densely informative, with the core purpose front-loaded and the pagination caveats earning their place given their real-world impact. It could be slightly tightened, but the length is justified by the complexity of eBay's search behavior.

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?

For a search tool with 11 parameters, no output schema, and only a readOnlyHint annotation, the description is remarkably complete: it explains what is returned, how to paginate correctly, how filters and currency behave, and which sibling tools are related. Nothing essential for correct invocation is missing.

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?

Although the schema covers all 11 parameters, the description meaningfully enriches them: offset must advance in whole limit-sized steps while hasNext is true, buyingOptions requires an explicit AUCTION value to reach auctions, and an unrecognized priceCurrency silently drops the filter rather than erroring. These are behaviors an agent could not infer from the schema alone.

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 opens with a specific verb and resource: "Search active eBay listings marketplace-wide." It immediately distinguishes itself from seller-owned inventory and names its counterpart ebay_find_completed_items, so an agent can tell exactly which use case this tool serves.

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 clearly scopes when to use the tool: marketplace-wide active listings, not the seller's own inventory, and identifies ebay_find_completed_items as the counterpart. It does not provide an exhaustive when-not-to-use list for every sibling, but the context is clear enough to route an agent correctly.

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

Deploy Server

Other Tools