Skip to main content
Glama

ebay_bulk_update_ads_bid_by_inventory_reference

Update bid percentages for multiple ads in CPS campaigns by specifying inventory reference ID and type. Streamline bid adjustments for SKU or item group ads through a single request.

Instructions

Update bid percentages for multiple ads by inventory reference. CPS campaigns only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID
adsYesBulk bid update request
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only mentions a bulk update but does not disclose whether the operation is idempotent, destructive, or if it has any side effects like overwriting existing bids. Missing critical behavioral traits 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 very short (two sentences) and front-loaded with the core purpose and constraint. However, it could include a bit more detail without harming conciseness.

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?

No output schema exists, and the description does not mention return values, error handling, or bulk limits. Given the complexity of the nested object and bulk operation, more contextual information would be helpful, but the purpose is adequately conveyed.

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%, with each parameter having a description. The description adds no additional meaning beyond the schema, so a baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action ('Update bid percentages'), resource ('multiple ads by inventory reference'), and a specific constraint ('CPS campaigns only'). This clearly distinguishes it from sibling tools like ebay_bulk_update_ads_bid_by_listing_id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly limits usage to CPS campaigns, providing a clear when-to-use condition. However, it does not specify when not to use (e.g., if not a CPS campaign) or offer alternatives, so it falls short of a perfect score.

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