Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_keyword

Read-only

Retrieve specific keyword details from an eBay marketing campaign by providing campaignId and keywordId. Use this to access keyword data via the eBay Marketing API.

Instructions

Get keyword through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordIdYeskeywordId required endpoint parameter
campaignIdYescampaignId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • changedInput schema / properties / keywordId / description
      Previous value: -"Keyword ID"New value: +"keywordId required endpoint parameter"
    • changedInput schema / required
      Previous value: -[
-  "campaignId",
-  "adGroupId",
-  "keywordId"
-]New value: +[
+  "campaignId",
+  "keywordId"
+]
  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",
-  "keywordId"
-]New value: +[
+  "campaignId",
+  "adGroupId",
+  "keywordId"
+]
  3. First observedv1.8.10

TDQS

C2.9/5.0
Behavior2/5

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

The description adds no behavioral detail beyond the annotation readOnlyHint: true. It does not mention authentication needs, rate limits, response behavior, or any side effects; it simply restates the read-only nature already captured by annotations.

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?

The description is a single short sentence with no padding, which is concise, but it mostly restates the tool name and adds little informative value. It is appropriately sized but under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple read-only operation, complete parameter schema, and readOnlyHint annotation, the description is minimally adequate. However, it does not describe the return value or clarify how it differs from ebay_get_keywords, leaving some context gaps.

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 is 100%, so the baseline is 3. The parameter descriptions in the schema only restate that keywordId and campaignId are required endpoint parameters, and the tool description provides no additional semantic meaning for either parameter.

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 uses a specific verb and resource ('Get keyword') and mentions the eBay Marketing API, making the basic operation clear. However, it does not differentiate from siblings like ebay_get_keywords or ebay_get_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 on when to use this tool versus alternatives such as ebay_get_keywords, ebay_create_keyword, or ebay_update_keyword. There are no context cues, exclusions, or alternative tool references.

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