Skip to main content
Glama

ebay_update_bid

Update bid percentage for an ad campaign using the eBay Marketing API.

Instructions

Update bid through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adIdYesadId required endpoint parameter
requestYesUpdate bid request body
campaignIdYescampaignId required endpoint parameter
Behavior1/5

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

With no annotations, the description carries full burden. It only says 'Update' but omits any behavioral traits: effect on existing bids, idempotency, permissions, return value, or side effects.

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, which is concise, but it lacks substance. It is under-informative rather than efficiently informative.

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?

For a mutation tool with 3 parameters and no output schema, the description is incomplete. It does not explain what the bid update entails, expected response, or how it fits into the advertising workflow.

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% (all parameters have descriptions), so baseline is 3. The description adds no meaning beyond the schema, which itself is generic (e.g., 'adId required endpoint parameter'). The nested 'bidPercentage' has no description.

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 'Update bid through the eBay Marketing API' identifies the resource (bid) and action (update), but 'bid' is ambiguous among sibling tools like ebay_update_ad_group or ebay_update_campaign_budget. It does not differentiate from bulk bid update tools or specify what kind of bid.

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 (e.g., bulk bid update tools). No prerequisites, context, or exclusions 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/YosefHayim/ebay-mcp'

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