Skip to main content
Glama

ebay_pause_campaign

Pause a running eBay marketing campaign to temporarily stop its delivery. Resume the campaign later without losing its settings.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID
Behavior4/5

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

Discloses that pausing is reversible, which is key behavioral info. With no annotations, the description carries the full burden; it covers the main effect (pausing) and future capability (resume). Could mention side effects but adequate for simple toggle.

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?

Two sentences, zero waste. First sentence states purpose, second adds critical detail about reversibility. Perfectly front-loaded and concise.

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

Completeness4/5

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

For a simple tool with one parameter and no output schema, the description covers the essential action and reversibility. Lacks mention of prerequisites (e.g., campaign must be running) or status if already paused, but still fairly complete.

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?

Schema provides 100% coverage for the single parameter (campaignId as 'Campaign ID'). Description adds no further meaning; 'campaignId' is self-explanatory. Baseline 3 is appropriate since schema does the work.

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?

Description clearly states 'Pause a running marketing campaign', specifying the verb and resource. It distinguishes from siblings like ebay_resume_campaign and ebay_end_campaign by implying reversibility and by explicitly targeting marketing campaigns, not promotions or items.

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?

Implies use for temporary stoppage by stating 'Campaign can be resumed later', but lacks explicit when-to-use or when-not-to-use guidance. No comparison to alternatives like ebay_end_campaign or ebay_pause_item_promotion.

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/YosefHayim/ebay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server