Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_resume_item_promotion

Resume a paused eBay item promotion using its promotion ID to reactivate its discount and visibility.

Instructions

Resume a paused item promotion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promotionIdYesPromotion ID
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are available, so the description must carry the full behavioral burden. It only states the action (resume) without disclosing effects, prerequisites (e.g., promotion must be paused), authorization needs, or idempotency. This is insufficient for safe agent invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one sentence) with no wasted words. It is concise but at the cost of omitting critical information, which prevents a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It fails to explain the effect on the promotion, required state, possible errors, or return behavior, leaving significant gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

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 parameter 'promotionId' (described as 'Promotion ID'). The tool description adds no extra meaning beyond the schema, so the score is at the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Resume' and the resource 'paused item promotion', matching the tool name. It distinguishes the tool from siblings like 'ebay_pause_item_promotion' by implying the reverse action. However, it does not explicitly differentiate from 'ebay_resume_promotion' or explain what constitutes an item promotion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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. Sibling tools like 'ebay_pause_item_promotion' and 'ebay_resume_promotion' exist, but the description offers no comparative context or prerequisites for use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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