Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_pause_campaign

Pause an active eBay marketing campaign to temporarily stop promotion while preserving campaign settings for later resumption.

Instructions

Pause a running marketing campaign. Campaign can be resumed later.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool pauses and can resume, but provides no details on side effects (e.g., impact on active ads, billing, state transitions) or prerequisites (e.g., campaign must be running). This is insufficient for a mutation tool.

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

Conciseness5/5

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

The description is extremely concise, consisting of two short sentences that front-load the core purpose and a key behavioral trait. No redundant information is present.

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 and output schema, the description should provide more context about prerequisites (e.g., campaign must be running), effects (e.g., what happens to ads), and state changes. The minimal two sentences leave significant gaps for a simple but stateful operation.

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 schema coverage is 100%, with a basic description for 'campaignId'. The tool description adds no additional meaning or context about the parameter beyond 'Campaign ID', so baseline score 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 action ('Pause') and the resource ('running marketing campaign'), and distinguishes from sibling tools like 'ebay_end_campaign' and 'ebay_resume_campaign' by noting the campaign can be resumed later. This prevents confusion with permanent termination.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for temporary pausing (since it mentions resumption), but does not explicitly state when to use this versus alternatives like 'ebay_end_campaign' for permanent stops. No exclusion criteria are provided.

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