ebay_end_campaign
End an active eBay marketing campaign by providing its campaign ID.
Instructions
End campaign through the eBay Marketing API.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | Yes | campaignId required endpoint parameter |
End an active eBay marketing campaign by providing its campaign ID.
End campaign through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | Yes | campaignId required endpoint parameter |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description is only 'End campaign through the eBay Marketing API.' It does not disclose any behavioral traits such as whether the campaign is permanently stopped, what happens to associated ads or budget, or if the action is reversible. For a potentially destructive action, this is insufficient.
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 a single sentence with no unnecessary words. It is front-loaded with the action 'End campaign'. However, it could be slightly more informative without sacrificing brevity, hence a 4.
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?
Given the significance of ending a campaign and the lack of output schema or annotations, the description is woefully incomplete. It fails to explain any prerequisites, side effects, or return behavior, leaving the agent with minimal guidance.
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?
The input schema has full coverage (100%) with a clear description for the only parameter 'campaignId'. The tool description does not add any additional meaning beyond what the schema provides, achieving a 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 'End campaign' which clearly indicates the action and resource. It differentiates from sibling tools like pause, resume, launch, and delete by the verb 'end'. However, it does not clarify what 'end' entails (e.g., permanent termination vs. archive) or distinguish it from 'delete_campaign' which also exists.
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 usage guidelines are provided. There is no indication of when to use this tool over alternatives like 'ebay_pause_campaign' or 'ebay_delete_campaign'. The agent has no context for appropriate scenarios or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/YosefHayim/ebay-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server