Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_update_ad_group

Update ad group details like name, default bid, and status in eBay marketing campaigns using the Marketing API.

Instructions

Update ad group through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesUpdate ad group request body
adGroupIdYesadGroupId required endpoint parameter
campaignIdYescampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.14.1
    • changedInput schema / properties / adGroupId / description
      Previous value: -"Ad Group ID"New value: +"adGroupId required endpoint parameter"
    • 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 ad group request body",
+  "properties": {
+    "adGroupStatus": {
+      "type": "string"
+    },
+    "defaultBid": {
+      "additionalProperties": false,
+      "properties": {
+        "currency": {
+          "type": "string"
+        },
+        "value": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / updateData
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Ad group update data",
-  "properties": {
-    "defaultBid": {
-      "additionalProperties": false,
-      "description": "New default bid",
-      "properties": {
-        "amount": {
-          "description": "Default bid amount",
-          "type": "string"
-        },
-        "currency": {
-          "description": "Currency code",
-          "type": "string"
-        }
-      },
-      "required": [
-        "amount",
-        "currency"
-      ],
-      "type": "object"
-    },
-    "name": {
-      "description": "New ad group name",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "adGroupId",
-  "updateData"
-]New value: +[
+  "adGroupId",
+  "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?

No annotations exist, so the description carries the full burden. It only says 'Update ad group' without disclosing whether it's a partial update, what fields are required, permissions needed, rate limits, or side effects. Minimal behavioral information.

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?

A single clear sentence, no wasted words. It is appropriately short, though could benefit from one more sentence on usage or behavior.

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 no annotations, the description should provide more context (e.g., return format, error handling, update semantics). It is insufficient for an agent to invoke correctly without guessing.

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% (all parameters have descriptions). The description adds no additional meaning beyond the schema (e.g., the 'request' description is just 'Update ad group request body'). Baseline 3 is appropriate.

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 action ('Update') and resource ('ad group'), with the API mention. It distinguishes from create/get/delete siblings by the verb, but does not differentiate from other update tools like ebay_update_ad or ebay_update_campaign_identification.

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 vs alternatives (e.g., ebay_create_ad_group, ebay_get_ad_group). No prerequisites 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