ebay_delete_ad
Delete a specific ad from an eBay campaign by providing the campaign and ad IDs.
Instructions
Delete a specific ad from a campaign.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | Yes | Campaign ID | |
| adId | Yes | Ad ID |
Delete a specific ad from an eBay campaign by providing the campaign and ad IDs.
Delete a specific ad from a campaign.
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | Yes | Campaign ID | |
| adId | Yes | Ad ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden for behavioral disclosure. It states 'delete' indicating mutation and destructiveness, but does not mention side effects, irreversibility, or permissions. Basic but not detailed.
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?
Single sentence with no extraneous information, efficiently conveys the tool's purpose.
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 with 2 parameters and no output schema, the description is sufficient. Minor gaps: does not note irreversibility or that the ad must belong to the campaign. Still, adequate for its simplicity.
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?
Input schema has 2 parameters with 100% description coverage, so schema already documents campaignId and adId. Description adds no extra meaning beyond the schema.
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?
Description clearly states 'Delete a specific ad from a campaign', using a specific verb and resource. It differentiates from sibling tools like ebay_bulk_delete_ads_by_inventory_reference which delete multiple ads.
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 explicit guidance on when to use this tool versus alternatives or prerequisites. Usage is implied as deleting a single ad, but lacks when-not-to-use info.
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