Retrieve item price markdown promotion details by providing a promotion ID. Use this to check current markdown campaign information via eBay Marketing API.
Get item price markdown promotion through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| promotionId | Yes | promotionId required endpoint parameter |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / promotionId / descriptionPrevious value: -"Promotion ID"New value: +"promotionId required endpoint parameter"v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=true already conveys that this is a safe read operation, and the description adds no further behavioral context. It does not mention potential failure modes, response format, or how to obtain the promotionId. While it does not contradict the annotation, it provides no additional transparency beyond the structured data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no unnecessary words. It states the verb and resource clearly. While it is minimal, it is appropriately sized for the simplicity of the action, though it could benefit from a bit more context without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is too bare for a tool within a large domain. It does not explain what a 'price markdown promotion' is, how to obtain a promotionId (e.g., from ebay_get_promotions), or what the response contains (since there is no output schema). It also lacks differentiation from similar tools like ebay_get_item_promotion, leaving an agent under-informed for correct usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage for the single parameter promotionId, so the baseline is 3. The tool description does not mention the parameter at all, and the schema description only notes it is required. No additional semantic meaning (e.g., format, source, examples) is provided beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the verb 'Get' and the specific resource 'item price markdown promotion', which is distinct from the broader 'item promotion' or 'promotions' tools. However, it does not explicitly differentiate itself from ebay_get_item_promotion, which could be confused. The resource name is specific enough that an agent can likely infer the purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like ebay_get_item_promotion or ebay_get_promotions. The description only states the basic action without mentioning any conditions, prerequisites, or exclusion criteria. An agent has to infer usage from the name and parameter alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.