Skip to main content
Glama

ebay_pause_promotion

Pause an active eBay promotion via the Marketing API by providing its promotionId to stop campaign activity and spending.

Instructions

Pause promotion through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promotionIdYespromotionId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.1
    • changedInput schema / properties / promotionId / description
      Previous value: -"Promotion ID"New value: +"promotionId required endpoint parameter"
  2. First observedv1.8.10

TDQS

B3.3/5.0
Behavior3/5

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

The annotations only indicate readOnlyHint=false, so the description's word 'Pause' adds a useful behavioral distinction: it's a state change, not a read operation, and not a destructive delete. However, it doesn't disclose side effects, reversibility, or whether pausing requires the promotion to be in a specific state, so there is room for more transparency.

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?

One short, front-loaded sentence with no filler. Every word earns its place, and for a one-parameter tool the length is perfectly appropriate.

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

Completeness3/5

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

For a simple pause operation with a single documented parameter and no output schema, the description provides the essential action. It is missing any note about expected response, side effects, or prerequisites, but it is minimally sufficient for an agent to attempt the call.

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 description coverage is 100%, so the schema already documents promotionId sufficiently. The description adds no additional meaning about what promotionId refers to or how to obtain it, which is acceptable under the baseline, but not more.

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 uses a specific verb ('Pause') and resource ('promotion'), making the core action clear. It is easily distinguishable from sibling tools like ebay_pause_campaign or ebay_resume_promotion, but it doesn't explicitly differentiate among the various promotion lifecycle tools (e.g., delete, end, resume), so it stops short of a perfect score.

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 given on when to use this tool versus alternatives such as ebay_resume_promotion, ebay_delete_item_promotion, or ebay_get_promotions. The only implied usage is the action itself; no prerequisites, conditions, or exclusions are mentioned.

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

Deploy Server

Other Tools