ebay_delete_ad
Remove a specific ad from an eBay campaign using campaign ID and ad ID.
Instructions
Delete a specific ad from a campaign.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| adId | Yes | Ad ID | |
| campaignId | Yes | Campaign ID |
Remove a specific ad from an eBay campaign using campaign ID and ad ID.
Delete a specific ad from a campaign.
| Name | Required | Description | Default |
|---|---|---|---|
| adId | Yes | Ad ID | |
| campaignId | Yes | Campaign ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It only states the deletion action without disclosing effects (e.g., irreversibility, impact on metrics, required permissions). This is insufficient for an agent to use safely.
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 very concise (one sentence). While front-loaded, it sacrifices necessary detail, making it too terse to be fully useful. Conciseness should not come at the cost of completeness.
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 simple delete operation, the description still lacks essential context like side effects, prerequisites, or return values. Given no output schema and many sibling tools, more completeness is needed.
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 coverage is 100%, but the description adds no meaning beyond the schema's parameter names and descriptions. Baseline score of 3 is appropriate since no extra value is provided.
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 clearly states the action (delete) and the resource (specific ad from a campaign). However, among many sibling delete tools (e.g., delete_campaign, delete_keyword), it does not differentiate itself, so it's only moderately clear.
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 on when to use this tool versus alternatives (e.g., bulk delete tools). No prerequisites or when-not-to-use context is given, leaving the agent without decision support.
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/jyarbro/ebay-seller-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server