Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_create_keyword

Create a keyword for an eBay ad campaign by providing campaign ID, ad group ID, keyword text, and match type. Optionally set a bid to control cost per click.

Instructions

Create keyword through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesCreate keyword request body
campaignIdYescampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.14.1
    • removedInput schema / properties / adGroupId
      Removed value: -{
-  "description": "Ad Group ID",
-  "type": "string"
-}
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign ID"New value: +"campaignId required endpoint parameter"
    • removedInput schema / properties / keyword
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Keyword configuration",
-  "properties": {
-    "bid": {
-      "additionalProperties": false,
-      "description": "Keyword-specific bid (overrides ad group default)",
-      "properties": {
-        "amount": {
-          "description": "Bid amount",
-          "type": "string"
-        },
-        "currency": {
-          "description": "Currency code",
-          "type": "string"
-        }
-      },
-      "required": [
-        "amount",
-        "currency"
-      ],
-      "type": "object"
-    },
-    "keywordText": {
-      "description": "Keyword text",
-      "type": "string"
-    },
-    "matchType": {
-      "description": "Keyword match type",
-      "enum": [
-        "BROAD",
-        "PHRASE",
-        "EXACT"
-      ],
-      "type": "string"
-    }
-  },
-  "required": [
-    "keywordText",
-    "matchType"
-  ],
-  "type": "object"
-}
    • addedInput schema / properties / request
      Added value: +{
+  "additionalProperties": false,
+  "description": "Create keyword request body",
+  "properties": {
+    "adGroupId": {
+      "type": "string"
+    },
+    "bid": {
+      "additionalProperties": false,
+      "properties": {
+        "currency": {
+          "type": "string"
+        },
+        "value": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "keywordText": {
+      "type": "string"
+    },
+    "matchType": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "adGroupId",
+    "keywordText",
+    "matchType"
+  ],
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "adGroupId",
-  "keyword"
-]New value: +[
+  "campaignId",
+  "request"
+]
  2. Changed2 schema fields changedv1.12.0
    • addedInput schema / properties / adGroupId
      Added value: +{
+  "description": "Ad Group ID",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "keyword"
-]New value: +[
+  "campaignId",
+  "adGroupId",
+  "keyword"
+]
  3. First observedv1.8.10

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits like whether it creates a single keyword, required permissions, or what happens if the keyword already exists. Minimal value beyond the name.

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?

Single sentence is very concise but too brief, lacking necessary details. It is efficient but under-specified, not earning extra points for 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?

Given the complexity (nested object, required parameters) and no output schema, the description is incomplete. It does not explain how keywords relate to campaigns or ads, leaving the agent with insufficient context.

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 brief descriptions for each parameter. The tool description adds no additional meaning beyond what the schema provides, but baseline is 3 given high coverage.

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 'Create keyword' which is a specific verb+resource. However, it does not distinguish from sibling tools like ebay_bulk_create_keyword or ebay_create_ad_by_listing_id, but the core action is clear.

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 such as ebay_bulk_create_keyword for batch creation. The description does not mention context 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