Suggest products for eBay marketing campaigns by providing a campaign ID, with optional category filters and pagination controls.
Suggest items through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | limit optional endpoint parameter | |
| offset | No | offset optional endpoint parameter | |
| campaignId | Yes | campaignId required endpoint parameter | |
| categoryIds | No | categoryIds optional endpoint parameter |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / campaignId / descriptionPrevious value: -"Campaign ID"New value: +"campaignId required endpoint parameter"Input schema / properties / categoryIdsAdded value: +{
+ "description": "categoryIds optional endpoint parameter",
+ "type": "string"
+}Input schema / properties / limitAdded value: +{
+ "description": "limit optional endpoint parameter",
+ "type": "number"
+}Input schema / properties / offsetAdded value: +{
+ "description": "offset optional endpoint parameter",
+ "type": "number"
+}v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=true discloses that this is a safe read operation, but the description itself adds no behavioral context. It does not explain whether suggestions are based on campaignId, whether they are generated in real-time, or what the response format is. With annotations present, the burden is lower, but a one-line generic statement still provides minimal transparency.
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 short and front-loaded with the verb, which is structurally efficient. However, its terseness sacrifices informative content. It is concise but not sufficiently informative for a tool with four parameters and no output schema.
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?
The description fails to provide essential context for an agent to call the tool correctly. It does not explain what 'suggest items' returns, how the required campaignId is used, or what the optional categoryIds, limit, and offset do. With no output schema and minimal context, an agent would be left guessing at the tool's purpose and behavior.
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 baseline is 3 even though the description provides no parameter details. However, the schema descriptions ('limit optional endpoint parameter') are tautological and add no meaning. The description does nothing to clarify how the parameters affect the suggestion behavior, so it stays at baseline.
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 verb ('suggest') and a resource ('items'), which gives some indication of the action hon the eBay Marketing API. However, it does not clarify what 'suggest items' means in practice—whether it returns recommendations for advertising, search, or something else—and it does not distinguish this tool from similar suggestions like ebay_suggest_bids or ebay_suggest_keywords.
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?
No guidance is provided about when to use this tool versus alternatives. The sibling list contains several suggestion-related tools (ebay_suggest_bids, ebay_suggest_keywords), but the description does not mention any selection criteria, context, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.