Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_update_campaign_identification

Update campaign identification via eBay Marketing API. Specify campaign ID and new campaign name to change campaign identifiers.

Instructions

Update campaign identification through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesUpdate campaign identification 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"
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Update campaign identification request body",
+  "properties": {
+    "campaignName": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / updateData
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Campaign identification data to update",
-  "properties": {
-    "campaignName": {
-      "description": "New campaign name",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "updateData"
-]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?

The description only says 'Update campaign identification,' which aligns with readOnlyHint=false but reveals nothing beyond it. No mention of side effects, reversibility, authorization requirements, or scope of changes. With minimal annotation coverage, the description fails to add behavioral context.

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 fluff, but 'through the eBay Marketing API' is redundant given the tool name already starts with 'ebay_'. It is front-loaded and appropriately brief, though the redundancy costs a small deduction.

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?

For a mutating tool with no output schema and only a basic readOnlyHint annotation, this description is inadequate. It does not explain what 'campaign identification' changes, when to use the tool, or how it differs from other campaign update tools. An agent must open the schema to understand basic purpose and parameters.

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% and both parameters (campaignId and request with campaignName) are described. The description adds no additional meaning about parameter format, behavior, or relationships beyond what the schema already provides.

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 states a specific action ('Update') and resource ('campaign identification'), which distinguishes it from sibling tools targeting budget, bidding strategy, or ads. However, 'campaign identification' is slightly ambiguous without reading the schema, so it doesn't fully name the exact field being updated.

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 such as ebay_update_campaign_budget or ebay_update_bidding_strategy. The description does not mention conditions, prerequisites, or exclusions.

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