Pause an eBay marketing campaign with a specified campaign ID to stop ad delivery and control advertising spend.
Pause campaign through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | Yes | campaignId required endpoint parameter |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / campaignId / descriptionPrevious value: -"Campaign ID"New value: +"campaignId required endpoint parameter"v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description does not disclose side effects, permission requirements, or what happens to the campaign after pausing (e.g., status change, interruption of ads).
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 wasted words. It is appropriately concise, though slightly too brief in context.
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 simplicity of the tool (one param, no output schema), the description should at least mention the effect of pausing or any prerequisites. It lacks this context.
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% with a well-described single parameter (campaignId). The description adds no extra meaning beyond what the schema provides, meeting the 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 clearly states the verb 'pause' and the resource 'campaign', distinguishing it from sibling tools like resume, end, or delete.
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., resume, end, or delete). The context of pausing is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.