Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_clone_ad

Clone an ad within a campaign to replicate its configuration and targeting, enabling quick duplication.

Instructions

Clone an ad within a campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adIdYesAd ID
campaignIdYesCampaign ID
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only says 'Clone', implying a copy operation, but fails to disclose side effects, dependencies (e.g., parent campaign must exist), or whether it's synchronous, what happens to the original, or permissions needed.

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

Conciseness3/5

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

Single sentence of 5 words is very concise but lacks structure. It doesn't include any summary of return value or additional context that would help the agent without being verbose.

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?

With no output schema, the description should explain what the tool returns (e.g., new ad ID). It doesn't mention outcomes, making it incomplete for an agent to correctly invoke and interpret results.

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 has 100% coverage with clear parameter descriptions ('Ad ID', 'Campaign ID'). The tool description adds no extra meaning beyond confirming the context ('within a campaign'), which is already implied by the schema.

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 'Clone an ad within a campaign' clearly states the action and resource, distinguishing it from sibling clone tools like 'ebay_clone_ad_group' and 'ebay_clone_campaign', but does not explicitly differentiate.

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 on when to use this tool vs alternatives (e.g., create_ad, update_ad). No conditions, prerequisites, or when-not-to-use instructions.

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