Delete an eBay item price markdown promotion via the Marketing API. Supply the promotionId to remove the discount campaign.
Delete item price markdown promotion through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| promotionId | Yes | promotionId required endpoint parameter |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / promotionId / descriptionPrevious value: -"Promotion ID"New value: +"promotionId required endpoint parameter"v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description matches destructiveHint=true and identifies the specific resource removed, but adds no further behavioral context such as irreversibility, active-promotion impact, auth, or rate limits.
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?
One short sentence front-loads the action and resource, with no wasted words or redundant elaboration.
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 one-parameter destructive tool with full schema coverage and matching annotations, the definition is sufficient to invoke correctly; no output schema is needed for this deletion.
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 already fully documents promotionId; the description adds no additional semantics about its format, source, or constraints, so the high-coverage baseline of 3 applies.
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 uses a specific verb ('Delete') and names the exact resource ('item price markdown promotion'), which distinguishes it from siblings like ebay_delete_item_promotion or create/update markdown tools.
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 on when to choose this tool over create/update or sibling delete tools; it simply states the action and leaves alternatives unaddressed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.