ebay_resume_promotion
Reactivate a paused eBay promotion to restore its active status and continue driving sales.
Instructions
Resume a paused promotion.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| promotionId | Yes | Promotion ID |
Reactivate a paused eBay promotion to restore its active status and continue driving sales.
Resume a paused promotion.
| Name | Required | Description | Default |
|---|---|---|---|
| promotionId | Yes | Promotion ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only implies state change from paused to active. Does not disclose side effects, error conditions, idempotency, or return values. For a mutation tool without annotations, more detail is needed.
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, no wasted words. Front-loaded with verb and resource. Appropriate for such a simple tool.
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 no output schema and no annotations, description lacks completeness. Does not explain what happens after resuming, if there is a response, or error handling. A more complete description would include expected state transitions.
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 covers 100% of parameters with basic description ('Promotion ID'). Description adds no extra meaning about where to find it or format. Baseline score is appropriate.
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 the action (Resume) and resource (paused promotion). It distinguishes from sibling pause tools like ebay_pause_promotion, though ebay_resume_item_promotion exists but is differentiated by resource (item promotion vs promotion).
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 use this tool, prerequisites (e.g., promotion must be paused), or alternatives. Does not mention that this resumes a promotion-level pause, not an item-level pause.
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