Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_update_ad_group_keywords

Update keywords for an ad group to refine targeting and improve campaign performance.

Instructions

Update keywords for an ad group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adGroupIdYesAd Group ID
campaignIdYesCampaign ID
updateDataYesKeyword update data
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only states 'Update keywords' without disclosing whether it replaces or merges, what permissions are needed, rate limits, or side effects. This is insufficient for a mutation tool.

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 concise sentence that is front-loaded with the key action. However, for a tool with a complex nested parameter, a slightly longer description could improve clarity without becoming verbose.

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 lack of output schema and complex input (updateData), the description is too minimal. It does not explain what the tool returns or how the updateData should be structured. The sibling tools with more detailed descriptions suggest more context 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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no additional meaning beyond the schema, particularly for the nested updateData object which could benefit from clarification on allowable fields.

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 the resource 'keywords for an ad group'. It distinguishes from siblings like ebay_update_keyword (singular) and ebay_update_ad_group (different resource). However, it does not specify what aspects of keywords can be updated, leaving some ambiguity.

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?

The description provides no guidance on when to use this tool versus alternatives such as ebay_update_keyword, ebay_bulk_update_keyword_bids, or ebay_create_keyword. There are no prerequisites or usage constraints mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jyarbro/ebay-seller-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server