Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_update_email_campaign

Update an eBay email campaign's subject, items, pricing, schedule, and audience with a single API call.

Instructions

Update email campaign through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesUpdate email campaign request body
emailCampaignIdYesemailCampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.14.1
    • removedInput schema / properties / emailCampaign
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Updated email campaign configuration",
-  "type": "object"
-}
    • changedInput schema / properties / emailCampaignId / description
      Previous value: -"Email campaign ID"New value: +"emailCampaignId required endpoint parameter"
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Update email campaign request body",
+  "properties": {
+    "audienceCodes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "categoryId": {
+      "type": "string"
+    },
+    "categoryType": {
+      "type": "string"
+    },
+    "itemIds": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "itemSelectMode": {
+      "type": "string"
+    },
+    "personalizedMessage": {
+      "type": "string"
+    },
+    "priceRange": {
+      "additionalProperties": false,
+      "properties": {
+        "maxPrice": {
+          "additionalProperties": false,
+          "properties": {
+            "currency": {
+              "type": "string"
+            },
+            "value": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "minPrice": {
+          "$ref": "#/properties/request/properties/priceRange/properties/maxPrice"
+        }
+      },
+      "type": "object"
+    },
+    "promotionId": {
+      "type": "string"
+    },
+    "promotionSelectModeEnum": {
+      "type": "string"
+    },
+    "scheduleDate": {
+      "type": "string"
+    },
+    "sort": {
+      "type": "string"
+    },
+    "subject": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "emailCampaignId",
-  "emailCampaign"
-]New value: +[
+  "emailCampaignId",
+  "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?

No annotations are present, so the description carries the full burden. It only states 'Update', implying mutation, but lacks details on side effects, required permissions, rate limits, or idempotency. 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.

Conciseness4/5

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

The description is very concise at one sentence, no unnecessary words. However, it could be structured with more detail in a compact format.

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?

No output schema and no explanation of return values or error handling. The input schema is complex with nested objects (priceRange), but the description provides no guidance on usage or expected results, leaving gaps for an AI agent.

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 the description adds no extra meaning beyond the schema's own descriptions. Baseline is 3, and the description does not provide additional semantic value for the parameters.

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 verb 'Update' and the resource 'email campaign' via the eBay Marketing API. It distinguishes from siblings like create and get, but could be more specific about what aspects of the campaign are updatable.

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 versus alternatives like create or delete. No prerequisites or context provided, leaving the agent without direction for selection.

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