Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_update_keyword

Idempotent

Update keyword bids or status in eBay marketing campaigns via the Marketing API. Adjust keyword settings to optimize ad performance.

Instructions

Update keyword through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesUpdate keyword request body
keywordIdYeskeywordId required endpoint parameter
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"
    • changedInput schema / properties / keywordId / description
      Previous value: -"Keyword ID"New value: +"keywordId required endpoint parameter"
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Update keyword request body",
+  "properties": {
+    "bid": {
+      "additionalProperties": false,
+      "properties": {
+        "currency": {
+          "type": "string"
+        },
+        "value": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "keywordStatus": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / updateData
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Keyword update data",
-  "properties": {
-    "bid": {
-      "additionalProperties": false,
-      "description": "New keyword bid",
-      "properties": {
-        "amount": {
-          "description": "Bid amount",
-          "type": "string"
-        },
-        "currency": {
-          "description": "Currency code",
-          "type": "string"
-        }
-      },
-      "required": [
-        "amount",
-        "currency"
-      ],
-      "type": "object"
-    },
-    "keywordText": {
-      "description": "New keyword text",
-      "type": "string"
-    },
-    "matchType": {
-      "description": "New match type",
-      "enum": [
-        "BROAD",
-        "PHRASE",
-        "EXACT"
-      ],
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "keywordId",
-  "updateData"
-]New value: +[
+  "campaignId",
+  "keywordId",
+  "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?

Annotations already declare readOnlyHint=false and idempotentHint=true, and the description adds no further behavioral context. It does not mention whether the update is partial, what fields are affected, what the response contains, or what side effects may occur.

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, efficient sentence with the core action front-loaded. It is concise and free of unnecessary filler, though it omits detail that would improve usefulness.

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, this description is incomplete. The agent is left without information about which keyword fields are updatable, how request.bid and keywordStatus interact, and how this differs from the bulk and negative-keyword variants.

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%, so the schema documents the three parameters, even though individual descriptions are mostly tautological (e.g., 'keywordId required endpoint parameter'). The tool description adds no parameter semantics beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the verb (Update) and resource (keyword) and provides API context (eBay Marketing API). It does not, however, distinguish this from closely related siblings like bulk_update_keyword or ebay_update_negative_keyword.

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 versus alternatives such as bulk_update_keyword, create_keyword, or ebay_update_negative_keyword. An agent cannot infer selection criteria from the description 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