Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_delete_ads_by_inventory_reference

Delete eBay ads identified by inventory reference ID and type from a specific campaign. Provide campaignId and inventory reference details to remove them via eBay Marketing API.

Instructions

Delete ads by inventory reference through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesDelete ads by inventory reference request body
campaignIdYescampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.14.1
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign ID"New value: +"campaignId required endpoint parameter"
    • removedInput schema / properties / inventoryReferenceId
      Removed value: -{
-  "description": "SKU or inventory item group key",
-  "type": "string"
-}
    • removedInput schema / properties / inventoryReferenceType
      Removed value: -{
-  "description": "Reference type",
-  "enum": [
-    "INVENTORY_ITEM",
-    "INVENTORY_ITEM_GROUP"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Delete ads by inventory reference request body",
+  "properties": {
+    "inventoryReferenceId": {
+      "type": "string"
+    },
+    "inventoryReferenceType": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "inventoryReferenceId",
-  "inventoryReferenceType"
-]New value: +[
+  "campaignId",
+  "request"
+]
  2. First observedv1.8.10

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations show readOnlyHint=false, and the description confirms a mutating delete operation. It does identify what is destroyed (ads by inventory reference), but it does not disclose whether the delete is permanent, whether it removes all matching ads, or what response the caller should expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence without filler. Every word contributes to identifying the operation and resource, making it easy to scan and parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a delete operation with no output schema, and the description leaves out important context such as whether the operation is irreversible, whether it deletes one ad or all ads tied to the inventory reference, and what happens if no ads match. The parameters are simple and well-covered by the schema, so the definition is minimally viable but not fully complete.

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 structured schema already documents campaignId and the request body. The description adds no additional meaning about inventoryReferenceType values, required formats, or relationships between campaignId and the inventory reference, leaving the agent to infer semantics from parameter names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Delete ads by inventory reference.' This clearly distinguishes the tool from ad-related siblings like get_ads_by_inventory_reference, update_bid, or bulk_delete_ads_by_listing_id, and the deletion scope is explicit.

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 about when to choose this tool over alternatives. It does not mention the bulk variants (bulk_delete_ads_by_inventory_reference), the single-ad delete (ebay_delete_ad), or any conditions that would make this specific endpoint the right choice.

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