Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_bulk_delete_ads_by_inventory_reference

Delete multiple eBay ads by inventory reference in a single API call to remove them from a campaign.

Instructions

Bulk delete ads by inventory reference through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesBulk delete ads by inventory reference 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": {
-    "inventoryReferences": {
-      "description": "Array of inventory references to delete",
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "inventoryReferenceId": {
-            "description": "SKU or inventory item group key",
-            "type": "string"
-          },
-          "inventoryReferenceType": {
-            "description": "Reference type",
-            "enum": [
-              "INVENTORY_ITEM",
-              "INVENTORY_ITEM_GROUP"
-            ],
-            "type": "string"
-          }
-        },
-        "required": [
-          "inventoryReferenceId",
-          "inventoryReferenceType"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "inventoryReferences"
-  ],
-  "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 inventory reference request body",
+  "properties": {
+    "requests": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "inventoryReferenceId": {
+            "type": "string"
+          },
+          "inventoryReferenceType": {
+            "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 description merely restates the action and API, adding no behavioral context beyond the readOnlyHint=false annotation. It does not disclose side effects, irreversibility, rate limits, or error behavior, which matters for a mutating bulk operation.

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 sentence with no fluff, but it essentially restates the tool name with the API context added. It is efficient but adds little informational value beyond the name.

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 mutation tool with a nested request body and no output schema, the description is too thin. It omits constraints on request count, response format, and failure behavior, leaving gaps for an agent trying to invoke the tool correctly.

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% for top-level parameters, so the baseline is 3. The parameter descriptions are largely tautological (e.g., 'campaignId required endpoint parameter') and the tool description adds no further meaning to the schema, so the score stays at 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 verb ('Bulk delete'), resource ('ads'), and the key qualifier ('by inventory reference'), which clearly differentiates it from siblings like ebay_bulk_delete_ads_by_listing_id. It does not explicitly name the sibling singular variant ebay_delete_ads_by_inventory_reference, but the word 'Bulk' covers that distinction, making the purpose evident.

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 provides no guidance on when to choose this tool over alternatives such as the non-bulk delete or the bulk delete by listing ID. It neither states conditions for use nor exclusions, leaving the agent to infer when it is appropriate.

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