Skip to main content
Glama

ebay_resume_campaign

Resume a paused eBay marketing campaign by supplying its campaign ID to restore ad delivery and maintain sales momentum.

Instructions

Resume campaign through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYescampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0
Behavior2/5

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

The description adds little beyond the readOnlyHint: false annotation. It does not disclose what resuming a campaign does, whether it changes status, requires a currently paused campaign, is idempotent, or what side effects occur.

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 a single short sentence that front-loads the core action. 'Through the eBay Marketing API' is mild boilerplate, but the overall structure is appropriately minimal for a one-parameter tool.

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?

While the schema fully documents the parameter, the overall context is thin for a mutating operation. There is no output schema and no explanation of campaign state transitions, prerequisites, or relationships to pause/launch/end, leaving the agent to infer critical behavior.

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 has 100% coverage for the single parameter, so the baseline is 3. However, the parameter description ('campaignId required endpoint parameter') is essentially redundant with the property name, and the tool description adds no additional semantic detail.

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 action ('Resume') and the resource ('campaign'), and the tool name reinforces this. It is distinguishable from siblings like ebay_pause_campaign and ebay_end_campaign, though it does not specify that this applies only to paused campaigns.

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?

There is no guidance on when to use this tool versus alternatives such as ebay_launch_campaign or ebay_pause_campaign. The description does not mention prerequisites, state requirements, or when not to use it.

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