Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_bulk_update_keyword_bids

Update bids for multiple keywords in a campaign to control advertising costs and improve performance.

Instructions

Update bids for multiple keywords.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsYesBulk keyword bid update request
campaignIdYesCampaign ID
Behavior2/5

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

With no annotations, the description carries the full burden. It only states 'update bids' without disclosing whether updates replace or merge, what happens on failure, rate limits, or idempotency. Critical behavioral details are missing.

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 very concise (4 words), which is efficient. However, it may be too terse, lacking necessary detail. It is well-structured as a single sentence.

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 tool's complexity (nested object for bulk updates, no output schema), the description is too minimal. It should mention that it updates bids in bulk, requires keyword IDs, and possibly the effect on existing bids.

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%, so the schema documents all parameters. The description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the description does not detract but offers no additional value.

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 'bids for multiple keywords'. It effectively distinguishes from the singular sibling 'ebay_update_keyword_bid', though it could be more explicit about the bulk nature.

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?

There is no guidance on when to use this tool versus alternatives like 'ebay_update_keyword_bid' or 'ebay_bulk_create_keywords'. No prerequisites, context, or exclusions are provided.

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