Skip to main content
Glama

commercebridge

by io.github.IsaiahDupree

Search eBay listings

search_ebay
Read-onlyIdempotent

Search live eBay listings by keyword and/or category across 8 sites (US, GB, DE, AU, CA, FR, IT, ES), built on eBay's official Browse API. Returns id, title, price, condition, seller feedback, shipping, image, categories, and URL per listing. Returns an honest credentials_required error until the upstream deployment has EBAY_CLIENT_ID/EBAY_CLIENT_SECRET provisioned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoKeyword query. Required unless `category` is given.
sortNo`price` = ascending, `-price` = descending.
limitNoDefault 20.
offsetNoDefault 0.
countryNoDefault us.
categoryNoeBay category id(s) to constrain the search.
currencyNoDefault USD.
priceMaxNo
priceMinNo
conditionNoCondition enum(s), comma-separated (e.g. NEW,USED).
freeShippingNo
buyingOptionsNoFIXED_PRICE and/or AUCTION, comma-separated.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds valuable context beyond annotations: it mentions the credential error behavior and the official API backend. No contradiction with annotations exists.

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 consists of three concise sentences: purpose and scope, output fields, and error behavior. Every sentence earns its place with no waste or redundancy.

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?

The description lists output fields, covers site scope, and discloses the credential error. Since there is no output schema, listing the returned fields is valuable. It does not explicitly state that q or category is required, but the schema covers that. Overall, it is fairly complete for a 12-parameter search 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?

Schema description coverage is 75%, so baseline is 3. The description adds only a high-level mention of keyword/category and the 8 sites, without diving into individual parameter meanings. It does not significantly improve parameter understanding over 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 it searches live eBay listings by keyword and/or category across 8 sites, built on eBay's official Browse API. It also lists the specific fields returned (id, title, price, condition, etc.), which differentiates it from sibling tools like search_ebay_sold and get_ebay_item by scope and output detail.

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 provides clear context (live listings, 8 sites, Browse API) but does not explicitly state when to use this tool versus alternatives like search_ebay_sold. No exclusions or comparisons are given, leaving the usage guidance implied but not explicit.

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

All commercebridge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools are clearly distinguished by platform and entity (e.g., get_etsy_shop vs get_etsy_listing), but search_shopify and search_shopify_products have overlapping purposes and near-identical names, which could cause misselection. The individual descriptions help, but the boundary is fuzzy.

Naming Consistency4/5

The dominant pattern is get_<platform>_<entity> and search_<platform>_<entity>, which is clear and consistent. However, deviations like search_shopify_products (which lists all products rather than performing a filtered search) and the use of plural get_ebay_items for bulk retrieval break the clean verb_noun convention in a few places.

Tool Count5/5

14 tools across four distinct platforms is well-scoped, with each platform getting a focused set of search and get operations. This is comfortably within the ideal range and each tool serves a concrete purpose.

Completeness4/5

The server provides solid read-only coverage for product search and detail retrieval across four platforms. Minor gaps exist, such as no way to fetch products within a Shopify collection or list Best Buy categories, but these are workaround-able and do not severely impair agent workflows.

Resources