Skip to main content
Glama

ebay_update_item_promotion

Update item promotion details on eBay, including discount rules, budget, and status. Modify existing promotions to optimize marketing campaigns via API.

Instructions

Update item promotion through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesUpdate item promotion request body
promotionIdYespromotionId required endpoint parameter
Behavior2/5

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

The description only states 'Update item promotion' implying mutation but does not disclose required permissions, rate limits, whether it performs partial or full update, or effects on active promotions. No annotations provided to compensate.

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 lacks structure. It is front-loaded with the verb 'Update', but the extreme brevity misses opportunities to provide essential details, making it minimally adequate.

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 complex input schema with nested objects, no output schema, and no annotations, the description is incomplete. It does not explain the promotionId parameter's role, what fields can be updated, or how to construct the request body.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning beyond the input schema. The schema itself has minimal descriptions (only 'request' object has a brief description), and most nested fields lack explanations. Schema description coverage is stated as 100% but many properties are not described, so the description fails to compensate.

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 'Update item promotion' which provides a specific verb and resource. It distinguishes the tool from sibling tools like ebay_create_item_promotion and ebay_get_item_promotion, but lacks additional context about what an item promotion is.

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 like ebay_update_item_price_markdown_promotion or ebay_create_item_promotion. No prerequisites or exclusions 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/YosefHayim/ebay-mcp'

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