Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_bulk_delete_ads_by_listing_id

Delete multiple eBay ads from a campaign by specifying their listing IDs. Streamline ad removal using the eBay Marketing API.

Instructions

Bulk delete ads by listing id through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesBulk delete ads by listing id 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 ad deletion request",
-  "properties": {
-    "listingIds": {
-      "description": "Array of listing IDs to delete",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "listingIds"
-  ],
-  "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 delete ads by listing id request body",
+  "properties": {
+    "requests": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "adId": {
+            "type": "string"
+          }
+        },
+        "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 only provide readOnlyHint=false, so the description carries responsibility for behavioral disclosure. 'Bulk delete' implies mutation, but there is no mention of permanence, whether the operation is atomic, or how success/failure is reported. The description adds almost nothing beyond what the verb 'delete' and the tool name already imply.

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 sentence with the action and resource front-loaded. 'Through the eBay Marketing API' is slightly redundant given the ebay_ prefix, but it is minor. The description is appropriately concise and readable.

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?

This tool has a nested request object and no output schema, yet the description does not explain how to populate request.requests[].adId or how campaignId relates to the operation. The listing-id versus adId ambiguity could lead an agent to construct an invalid call. Overall, the description is insufficient 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%, so the baseline is 3. The description adds no meaningful parameter detail beyond the schema, and it may even mislead by saying 'by listing id' while the request schema requires adId. The schema's own descriptions are low-value, but full coverage keeps this at the baseline.

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 ('Bulk delete ads') and resource ('ads by listing id'), which broadly distinguishes it from deletion by inventory reference. However, the phrase 'by listing id' conflicts with the schema's adId property, creating ambiguity about which identifier is actually used. The core purpose is still understandable but slightly imprecise.

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 given on when to use this tool instead of alternatives like ebay_delete_ad or ebay_bulk_delete_ads_by_inventory_reference. The description states only the operation itself, with no prerequisites, exclusions, or decision criteria. Any usage context must be inferred from the tool 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