Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_create_email_campaign

Create eBay email campaigns using the Marketing API, specifying campaign type, audiences, items, and schedule date.

Instructions

Create email campaign through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesCreate email campaign request body
marketplaceIdYesMarketplace ID sent as X-EBAY-C-MARKETPLACE-ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.14.1
    • removedInput schema / properties / emailCampaign
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Email campaign configuration",
-  "properties": {
-    "campaignName": {
-      "description": "Email campaign name",
-      "type": "string"
-    },
-    "marketplaceId": {
-      "description": "Marketplace ID",
-      "enum": [
-        "EBAY_AT",
-        "EBAY_AU",
-        "EBAY_BE",
-        "EBAY_CA",
-        "EBAY_CH",
-        "EBAY_CN",
-        "EBAY_CZ",
-        "EBAY_DE",
-        "EBAY_DK",
-        "EBAY_ES",
-        "EBAY_FI",
-        "EBAY_FR",
-        "EBAY_GB",
-        "EBAY_GR",
-        "EBAY_HK",
-        "EBAY_HU",
-        "EBAY_ID",
-        "EBAY_IE",
-        "EBAY_IL",
-        "EBAY_IN",
-        "EBAY_IT",
-        "EBAY_JP",
-        "EBAY_MY",
-        "EBAY_NL",
-        "EBAY_NO",
-        "EBAY_NZ",
-        "EBAY_PE",
-        "EBAY_PH",
-        "EBAY_PL",
-        "EBAY_PR",
-        "EBAY_PT",
-        "EBAY_RU",
-        "EBAY_SE",
-        "EBAY_SG",
-        "EBAY_TH",
-        "EBAY_TW",
-        "EBAY_US",
-        "EBAY_VN",
-        "EBAY_ZA",
-        "EBAY_HALF_US",
-        "EBAY_MOTORS_US"
-      ],
-      "type": "string"
-    },
-    "subject": {
-      "description": "Email subject line",
-      "type": "string"
-    }
-  },
-  "required": [
-    "campaignName",
-    "marketplaceId"
-  ],
-  "type": "object"
-}
    • addedInput schema / properties / marketplaceId
      Added value: +{
+  "description": "Marketplace ID sent as X-EBAY-C-MARKETPLACE-ID",
+  "type": "string"
+}
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Create email campaign request body",
+  "properties": {
+    "audiences": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "audienceType": {
+            "type": "string"
+          },
+          "code": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "emailCampaignType": {
+      "type": "string"
+    },
+    "itemIds": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "marketplaceId": {
+      "type": "string"
+    },
+    "scheduleDate": {
+      "type": "string"
+    },
+    "scheduleDateType": {
+      "type": "string"
+    },
+    "subject": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "emailCampaignType",
+    "marketplaceId"
+  ],
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "emailCampaign"
-]New value: +[
+  "marketplaceId",
+  "request"
+]
  2. First observedv1.8.10

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only mentions 'Create' and the API, but does not disclose any behavioral traits such as required permissions, side effects, or whether it is destructive.

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, concise sentence with no unnecessary words. However, it is under-specified, though this is more a completeness issue than structure. It is front-loaded with the verb and resource.

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 the complexity (nested objects, no output schema), the description is minimal. It does not explain what the tool returns, any side effects, or how to interpret the response. The agent may lack crucial context.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no additional meaning beyond the API name, but the schema itself is adequate. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Create' and the resource 'email campaign', specifically via the 'eBay Marketing API'. This distinguishes it from sibling tools like ebay_get_email_campaigns or ebay_update_email_campaign.

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 information is provided about when to use this tool versus alternatives, nor any prerequisites or context for its use. The agent receives no guidance on appropriate scenarios.

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