Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_bulk_update_ads_bid_by_inventory_reference

Bulk update ad bid percentages for multiple inventory references in an eBay campaign to adjust marketing spend per listing.

Instructions

Bulk update ads bid by inventory reference through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesBulk update ads bid 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 bid update request",
-  "properties": {
-    "requests": {
-      "description": "Array of bid update requests",
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "bidPercentage": {
-            "description": "New bid percentage (e.g., \"10.5\")",
-            "type": "string"
-          },
-          "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",
-          "bidPercentage"
-        ],
-        "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 bid by inventory reference request body",
+  "properties": {
+    "requests": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "bidPercentage": {
+            "type": "string"
+          },
+          "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

B3.2/5.0
Behavior2/5

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

The annotation readOnlyHint=false already conveys that this is a mutating operation. The description adds no additional behavioral context such as permissions required, idempotency, partial failure behavior, or effects on existing ads. For a mutation tool without a destructiveHint annotation, more disclosure is needed.

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 with no filler. It communicates the core operation immediately, and the trailing 'through the eBay Marketing API' adds minimal but acceptable context.

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?

The definition is too thin for a bulk mutation tool with nested request objects and no output schema. It omits expected values for bidPercentage, valid inventoryReferenceType options, and behavioral outcomes. An agent would likely need external API knowledge to invoke it 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 for the two top-level parameters is 100%, so the baseline is 3. The description does not add meaning beyond the schema, and nested fields like inventoryReferenceType and bidPercentage lack value format or allowed-value explanation, but the schema already names them clearly.

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 ('bulk update'), resource ('ads bid'), and identifier type ('by inventory reference'). This clearly distinguishes it from sibling tools like ebay_bulk_update_ads_bid_by_listing_id and related inventory-reference bulk operations.

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 about when to use this tool instead of alternatives such as ebay_bulk_update_ads_bid_by_listing_id, ebay_update_bid, or ebay_bulk_create_ads_by_inventory_reference. The description implies the operation but does not state context, prerequisites, or exclusions.

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