Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_pause_item_promotion

Pause an active eBay item promotion to temporarily stop its display, allowing resumption later without recreating the promotion.

Instructions

Pause a running item promotion. Can be resumed later.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promotionIdYesPromotion ID
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the basic effect (pause) and that the promotion can be resumed, but omits side effects, permission requirements, or whether any existing schedules are affected.

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 concise at two sentences, with no extraneous information. The key points are front-loaded, but the minimalism slightly reduces informativeness.

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 lack of annotations, an output schema, and the simplicity of the tool, the description should at least mention expected results (e.g., success/failure) or state the resulting promotion status. The current description is incomplete for safe invocation.

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 single parameter 'promotionId' is fully described in the schema as 'Promotion ID'. The description adds no additional context beyond the schema, and with 100% schema coverage, a baseline of 3 is appropriate.

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

Purpose5/5

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 'running item promotion', and adds the nuance 'Can be resumed later', which distinguishes it from deletion. The tool name is descriptive, and the description avoids tautology.

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?

The description lacks any guidance on when to use this tool versus alternatives like ebay_pause_campaign or ebay_pause_promotion. It does not specify prerequisites (e.g., promotion must be in 'running' state) or exclusions.

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