ebay_clone_ad
Clone an existing ad within a specific eBay campaign to create a duplicate for reuse.
Instructions
Clone an ad within a campaign.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | Yes | Campaign ID | |
| adId | Yes | Ad ID |
Clone an existing ad within a specific eBay campaign to create a duplicate for reuse.
Clone an ad within a campaign.
| Name | Required | Description | Default |
|---|---|---|---|
| campaignId | Yes | Campaign ID | |
| adId | Yes | Ad ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral disclosure. 'Clone' implies duplication but does not specify whether the original ad remains unchanged, what fields are copied, or if any constraints apply.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (5 words) and to the point, but it lacks sufficient detail to be fully informative. It is not wasteful, but it may be overly brief.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple 2-parameter input and no output schema, the description minimally explains the operation. It does not state the result (e.g., a new ad ID) or any side effects, leaving gaps for the agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Both parameters have schema descriptions (campaignId and adId), providing 100% coverage. The description adds no extra meaning beyond the parameter names and schema, meeting the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Clone an ad within a campaign' uses a specific verb ('clone') and resource ('ad'), clearly distinguishing it from siblings like ebay_clone_ad_group or ebay_clone_campaign.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like ebay_create_ad or ebay_clone_ad_group. No prerequisites or context for cloning are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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