ebay_resume_campaign
Resume a paused eBay marketing campaign to restart its delivery.
Instructions
Resume a paused marketing campaign. Campaign will start running again.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | Yes | Campaign ID |
Resume a paused eBay marketing campaign to restart its delivery.
Resume a paused marketing campaign. Campaign will start running again.
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | Yes | Campaign ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It states that the campaign will start running again, which is the expected behavior. However, it does not disclose what happens if the campaign is already running or if there are any prerequisites, which is acceptable for a simple mutation but leaves some ambiguity.
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 extremely concise with two short sentences that convey the essential information without any unnecessary words or redundancy.
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 low complexity (single parameter, no output schema, no annotations), the description is nearly complete. It could explicitly state the precondition that the campaign must be paused, but the current wording is sufficient for a straightforward resume operation.
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 100% description coverage for the single 'campaignId' parameter, so the description does not need to add additional semantics. It provides no extra meaning beyond what the schema already states, meeting the baseline expectation.
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 uses a specific verb 'Resume' and identifies the resource as a 'paused marketing campaign', clearly distinguishing it from sibling tools like 'ebay_pause_campaign' and 'ebay_end_campaign'.
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?
The description implies the tool is for campaigns that are currently paused, but does not explicitly state when not to use it or mention alternatives. The context from sibling tools provides some guidance, but formal usage guidelines are absent.
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