Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_keywords

Read-only

Retrieve keywords for an eBay marketing campaign through the Marketing API. Filter by ad group or keyword status to optimize campaign performance.

Instructions

Get keywords through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNolimit optional endpoint parameter
offsetNooffset optional endpoint parameter
adGroupIdsNoadGroupIds optional endpoint parameter
campaignIdYescampaignId required endpoint parameter
keywordStatusNokeywordStatus optional endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.14.1
    • removedInput schema / properties / adGroupId
      Removed value: -{
-  "description": "Ad group ID to filter by",
-  "type": "string"
-}
    • addedInput schema / properties / adGroupIds
      Added value: +{
+  "description": "adGroupIds optional endpoint parameter",
+  "type": "string"
+}
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign ID"New value: +"campaignId required endpoint parameter"
    • changedInput schema / properties / keywordStatus / description
      Previous value: -"Filter by keyword status: ACTIVE, PAUSED, or ARCHIVED"New value: +"keywordStatus optional endpoint parameter"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"limit optional endpoint parameter"
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip"New value: +"offset optional endpoint parameter"
  2. Changed3 schema fields changedv1.12.0
    • addedInput schema / properties / adGroupId
      Added value: +{
+  "description": "Ad group ID to filter by",
+  "type": "string"
+}
    • removedInput schema / properties / adGroupIds
      Removed value: -{
-  "description": "Comma-separated ad group IDs to filter by",
-  "type": "string"
-}
    • addedInput schema / properties / keywordStatus
      Added value: +{
+  "description": "Filter by keyword status: ACTIVE, PAUSED, or ARCHIVED",
+  "type": "string"
+}
  3. First observedv1.8.10

TDQS

C2.5/5.0
Behavior2/5

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

The description only repeats the name and does not disclose any behavioral details like pagination, sorting, or default limits. With readOnlyHint true, the description adds no extra context beyond what annotations already provide.

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 sentence with no fluff, but it lacks substantive information. It is concise but not informative, making it minimally acceptable.

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?

The description is too sparse for a tool with 5 parameters and no output schema. It does not mention what the response contains, whether results are paginated, or how to interpret the keyword status field. Given the sibling tools and marketing API context, more detail is needed.

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 documented in the schema with generic descriptions like 'optional endpoint parameter,' and the description adds no additional meaning. It does not explain the relationship between parameters (e.g., campaignId is required) or their purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear action: retrieving keywords via the eBay Marketing API. However, it does not specify the scope (e.g., per campaign) or differentiate from siblings like ebay_get_keyword, which retrieves a single keyword, making it ambiguous which tool to use when.

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 ebay_get_keyword or other keyword-related tools. There is no mention of context such as retrieving all keywords for a campaign or filtering criteria.

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