Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_bulk_update_ads_bid_by_inventory_reference

Update multiple eBay ad bids in bulk by inventory reference to manage campaign bid percentages efficiently.

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/5.0
Behavior2/5

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

No annotations provided, and the description only mentions 'bulk update ads bid'. Does not disclose idempotency, side effects, permissions, or error behavior. Minimal behavioral disclosure.

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

Conciseness3/5

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

A single sentence, concise but lacks structure. It does not front-load the most critical details, but it is not verbose.

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 tool with nested parameters and no output schema or annotations, the description is too brief. It does not explain the request structure, bid percentage semantics, or what the response contains.

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 coverage is 100% with descriptions for each parameter. The description adds no new meaning beyond the schema. Baseline score of 3 is appropriate.

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 clearly states the verb 'bulk update', the resource 'ads bid', and the method 'by inventory reference'. It distinguishes from sibling tools like ebay_bulk_update_ads_bid_by_listing_id.

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 on when to use this tool versus alternatives (e.g., updating by listing ID). The description only states what it does, not when to prefer it.

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