Search eBay listings by keyword and return normalized JSON results with pagination, item limits, and listing-type filters for active, sold, completed, or sold-completed items.
Search eBay listings. Returns normalized eBay search results.
| Name | Required | Description | Default |
|---|---|---|---|
| option | Yes | eBay search payload |
Changes observed during successful MCP inspections.
v1.17.5Input schema / properties / option / propertiesAdded value: +{
+ "keyword": {
+ "description": "keyword to search on Ebay",
+ "type": "string"
+ },
+ "limit": {
+ "description": "Number of items per page",
+ "enum": [
+ 60,
+ 120,
+ 240
+ ],
+ "type": "integer"
+ },
+ "listing_type": {
+ "description": "Listing type to search",
+ "enum": [
+ "active",
+ "sold",
+ "completed",
+ "sold_completed"
+ ],
+ "type": "string"
+ },
+ "page": {
+ "description": "Page number",
+ "type": "integer"
+ }
+}Input schema / properties / option / requiredAdded value: +[
+ "keyword"
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it returns 'normalized' results, without detailing pagination behavior, rate limits, or what normalization entails. This is minimal disclosure for a search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, consisting of two short sentences. The primary purpose is front-loaded in the first sentence, and the second adds a detail about output normalization. There is no wasted wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a search tool with no output schema, the description lacks essential context. It does not explain the structure of the returned results, how pagination works, or what 'normalized' means in practice. An agent might need more detail to correctly interpret and use the output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters (keyword, page, limit, listing_type). The description adds no extra meaning about parameter usage or constraints, so it does not exceed the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear purpose: 'Search eBay listings.' It also mentions the output is 'normalized eBay search results,' which adds specificity. However, it does not explicitly distinguish this tool from sibling search tools like ebay_item or ebay_seller, leaving the differentiation implicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. There are many eBay-related siblings (e.g., ebay_item, ebay_seller, ebay_live_streams_batch), and the description does not clarify which scenarios warrant this search function. Usage is 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.