Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_clone_campaign

Clone an eBay marketing campaign using the original campaign ID and a request body with new name, dates, and funding strategy.

Instructions

Clone campaign through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesClone campaign request body
campaignIdYescampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.14.1
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign ID"New value: +"campaignId required endpoint parameter"
    • removedInput schema / properties / cloneData
      Removed value: -{
-  "additionalProperties": false,
-  "description": "New campaign settings",
-  "properties": {
-    "campaignName": {
-      "description": "Name for the cloned campaign",
-      "type": "string"
-    },
-    "endDate": {
-      "description": "End date (ISO 8601 format)",
-      "type": "string"
-    },
-    "fundingStrategy": {
-      "additionalProperties": false,
-      "properties": {
-        "bidPercentage": {
-          "description": "Bid percentage (e.g., \"10.5\")",
-          "type": "string"
-        },
-        "fundingModel": {
-          "enum": [
-            "COST_PER_SALE",
-            "COST_PER_CLICK"
-          ],
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "startDate": {
-      "description": "Start date (ISO 8601 format)",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Clone campaign request body",
+  "properties": {
+    "campaignName": {
+      "type": "string"
+    },
+    "endDate": {
+      "type": "string"
+    },
+    "fundingStrategy": {
+      "additionalProperties": false,
+      "properties": {
+        "bidPercentage": {
+          "type": "string"
+        },
+        "fundingModel": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "startDate": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "campaignName"
+  ],
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "cloneData"
-]New value: +[
+  "campaignId",
+  "request"
+]
  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?

With no annotations, the description must disclose behavioral traits. It only states the action (clone) without details on side effects, required permissions, rate limits, or whether it creates the campaign immediately. The minimal description fails to inform the agent about consequences.

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 sentence, very concise and front-loaded with the action. It earns its place, though it could include more critical details without becoming overly 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?

Given no output schema and nested parameters, the description lacks completeness. It does not explain what the clone operation entails, what the response format is, or any preconditions (e.g., the campaign must exist). The agent is left with an incomplete picture.

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 coverage is 100%, so baseline is 3. The description adds no extra meaning to the parameters beyond what the schema already provides (e.g., campaignId and request descriptions). It does not enhance parameter understanding.

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 tool clones a campaign via the eBay Marketing API, specifying a verb and resource. However, among many sibling campaign tools (create, get, delete, etc.), it doesn't differentiate 'clone' from 'create' explicitly, missing some specificity.

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 provided on when to use this tool versus alternatives like ebay_create_campaign or ebay_get_campaign. No prerequisites, context, 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