Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_bulk_update_ads_status

Update multiple ad statuses in one call via eBay Marketing API. Provide campaign ID and bulk request to change ad statuses.

Instructions

Bulk update ads status through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesBulk update ads status request body
campaignIdYescampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.14.1
    • removedInput schema / properties / ads
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Bulk status update request",
-  "properties": {
-    "requests": {
-      "description": "Array of status update requests",
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "adId": {
-            "description": "Ad ID",
-            "type": "string"
-          },
-          "adStatus": {
-            "description": "New ad status",
-            "enum": [
-              "ACTIVE",
-              "PAUSED",
-              "ARCHIVED"
-            ],
-            "type": "string"
-          }
-        },
-        "required": [
-          "adId",
-          "adStatus"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "requests"
-  ],
-  "type": "object"
-}
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign ID"New value: +"campaignId required endpoint parameter"
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Bulk update ads status request body",
+  "properties": {
+    "requests": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "adStatus": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "adStatus"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "ads"
-]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 annotations provide readOnlyHint=false, indicating a write operation, and the description consistently says 'update'. However, it adds no further behavioral detail such as required permissions, side effects on existing data, rate limits, or response characteristics.

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. It is front-loaded with the key action and resource, though it is brief to the point of being vague on details.

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 nested request object and no output schema, the description is minimal. It does not explain valid adStatus values, the structure of the request array, or how this tool differs from similar bulk update tools. The lack of context makes it incomplete for correct invocation.

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% as both campaignId and request have descriptions. The tool description adds no additional parameter meaning beyond the schema, so it meets the baseline of 3.

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 the verb 'update' and the resource 'ads status' and mentions the eBay Marketing API. It is clear what the tool does, but it does not distinguish from the sibling tool 'ebay_bulk_update_ads_status_by_listing_id' which appears nearly identical, so it lacks differentiation.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or exclusions, leaving the agent to infer usage context from the name alone.

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