ebay_clone_package
Duplicate an existing package by providing its ID to create an identical copy for reuse.
Instructions
Clone a package to create a duplicate
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| packageId | Yes | The package ID to clone |
Duplicate an existing package by providing its ID to create an identical copy for reuse.
Clone a package to create a duplicate
| Name | Required | Description | Default |
|---|---|---|---|
| packageId | Yes | The package ID to clone |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description fails to disclose behavioral details such as whether the original is affected, depth of cloning, or any restrictions. For a mutation tool, this is insufficient.
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 a single sentence, which is concise but lacks necessary detail. It does not waste words but also does not provide value beyond the name.
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 complexity of a clone operation, the description is too brief. It does not explain what cloning entails, what fields are duplicated, or what the outcome is, especially with no output schema.
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?
Schema coverage is 100% with a single parameter 'packageId' described as 'The package ID to clone'. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.
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 a package to create a duplicate' clearly states the action (clone) and resource (package). It differentiates from sibling clone tools like ebay_clone_ad and ebay_clone_campaign by specifying the resource type.
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. Lacks context about prerequisites, conditions, or scenarios where cloning is appropriate.
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