Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_update_keyword

Update keywords in eBay marketing campaigns. Adjust bid amounts or keyword status to refine ad targeting and 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?

No annotations provided, so description must disclose behavior. It only states 'Update', implying mutation, but does not clarify if updates are partial/overwriting, immediate, reversible, or any side effects. Schema shows optional fields, suggesting partial updates, but this is not stated.

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?

Single sentence is concise, but it omits important details such as which keyword properties can be updated or typical usage patterns. Could be slightly expanded without losing conciseness.

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?

No output schema or annotations, so description should provide more context. It does not explain return values, error conditions, or how this update relates to other keyword operations. Siblings like bulk_update suggest batch operations, but no comparison.

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?

All parameters are described in the input schema (100% coverage), including nested fields like bid and keywordStatus. The description adds no additional meaning beyond what the schema provides, so baseline score applies.

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?

Description states verb 'Update' and resource 'keyword', indicating the tool modifies an existing keyword. However, it lacks specificity about what fields can be updated (e.g., bid, status) and does not distinguish from sibling tools like ebay_create_keyword or ebay_bulk_update_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 on when to use this tool versus alternatives like ebay_bulk_update_keyword. Does not mention required parameters (campaignId, keywordId, request) or any prerequisites for using the tool.

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