Set up a price markdown promotion for eBay listings to offer discounts, define eligible inventory, and schedule the campaign.
Create item price markdown promotion through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Create item price markdown promotion request body |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / promotionRemoved value: -{
- "additionalProperties": false,
- "description": "Markdown promotion configuration",
- "properties": {
- "discountPercentage": {
- "description": "Discount percentage (e.g., \"20\")",
- "type": "string"
- },
- "endDate": {
- "description": "End date (ISO 8601 format)",
- "type": "string"
- },
- "marketplaceId": {
- "description": "Marketplace ID",
- "enum": [
- "EBAY_AT",
- "EBAY_AU",
- "EBAY_BE",
- "EBAY_CA",
- "EBAY_CH",
- "EBAY_CN",
- "EBAY_CZ",
- "EBAY_DE",
- "EBAY_DK",
- "EBAY_ES",
- "EBAY_FI",
- "EBAY_FR",
- "EBAY_GB",
- "EBAY_GR",
- "EBAY_HK",
- "EBAY_HU",
- "EBAY_ID",
- "EBAY_IE",
- "EBAY_IL",
- "EBAY_IN",
- "EBAY_IT",
- "EBAY_JP",
- "EBAY_MY",
- "EBAY_NL",
- "EBAY_NO",
- "EBAY_NZ",
- "EBAY_PE",
- "EBAY_PH",
- "EBAY_PL",
- "EBAY_PR",
- "EBAY_PT",
- "EBAY_RU",
- "EBAY_SE",
- "EBAY_SG",
- "EBAY_TH",
- "EBAY_TW",
- "EBAY_US",
- "EBAY_VN",
- "EBAY_ZA",
- "EBAY_HALF_US",
- "EBAY_MOTORS_US"
- ],
- "type": "string"
- },
- "name": {
- "description": "Promotion name",
- "type": "string"
- },
- "startDate": {
- "description": "Start date (ISO 8601 format)",
- "type": "string"
- }
- },
- "required": [
- "name",
- "marketplaceId",
- "startDate",
- "endDate"
- ],
- "type": "object"
-}Input schema / properties / requestAdded value: +{
+ "additionalProperties": false,
+ "description": "Create item price markdown promotion request body",
+ "properties": {
+ "applyFreeShipping": {
+ "type": "boolean"
+ },
+ "autoSelectFutureInventory": {
+ "type": "boolean"
+ },
+ "blockPriceIncreaseInItemRevision": {
+ "type": "boolean"
+ },
+ "description": {
+ "type": "string"
+ },
+ "endDate": {
+ "type": "string"
+ },
+ "marketplaceId": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "priority": {
+ "type": "string"
+ },
+ "promotionImageUrl": {
+ "type": "string"
+ },
+ "promotionStatus": {
+ "type": "string"
+ },
+ "selectedInventoryDiscounts": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "discountBenefit": {
+ "additionalProperties": false,
+ "properties": {
+ "amountOffItem": {
+ "additionalProperties": false,
+ "properties": {
+ "currency": {
+ "type": "string"
+ },
+ "value": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "amountOffOrder": {
+ "$ref": "#/properties/request/properties/selectedInventoryDiscounts/items/properties/discountBenefit/properties/amountOffItem"
+ },
+ "percentageOffItem": {
+ "type": "string"
+ },
+ "percentageOffOrder": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "discountId": {
+ "type": "string"
+ },
+ "inventoryCriterion": {
+ "additionalProperties": false,
+ "properties": {
+ "inventoryCriterionType": {
+ "type": "string"
+ },
+ "inventoryItems": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "inventoryReferenceId": {
+ "type": "string"
+ },
+ "inventoryReferenceType": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "listingIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "ruleCriteria": {
+ "additionalProperties": false,
+ "properties": {
+ "excludeInventoryItems": {
+ "items": {
+ "$ref": "#/properties/request/properties/selectedInventoryDiscounts/items/properties/inventoryCriterion/properties/inventoryItems/items"
+ },
+ "type": "array"
+ },
+ "excludeListingIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "markupInventoryItems": {
+ "items": {
+ "$ref": "#/properties/request/properties/selectedInventoryDiscounts/items/properties/inventoryCriterion/properties/inventoryItems/items"
+ },
+ "type": "array"
+ },
+ "markupListingIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "selectionRules": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "brands": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "categoryIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "categoryScope": {
+ "type": "string"
+ },
+ "listingConditionIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "maxPrice": {
+ "$ref": "#/properties/request/properties/selectedInventoryDiscounts/items/properties/discountBenefit/properties/amountOffItem"
+ },
+ "minPrice": {
+ "$ref": "#/properties/request/properties/selectedInventoryDiscounts/items/properties/discountBenefit/properties/amountOffItem"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+ },
+ "ruleOrder": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "startDate": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Input schema / requiredPrevious value: -[
- "promotion"
-]New value: +[
+ "request"
+]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint: false, so the write nature is already known. The description adds no behavioral context beyond that – no mention of side effects, prerequisites (e.g., existing discounts), idempotency, or what happens on creation. Since the description carries no extra behavioral disclosure, this is a low score.
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 single sentence is front-loaded with the verb and resource and contains no filler. It is concise, though it sacrifices useful detail. The structure is clean, but the minimalism borders on under-specification.
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?
This is a complex creation tool with a nested request object, no output schema, and no field descriptions beyond the top-level parameter. The one-line description does not explain required subfields, valid values, or any setup needed (e.g., discount IDs). An agent cannot reliably construct a valid request from this definition alone.
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?
Schema description coverage is 100% because the 'request' property has a description, but that description ('Create item price markdown promotion request body') is tautological and provides no field-level meaning. The tool description adds no parameter information, so by the high-coverage baseline rule, a 3 is appropriate.
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 uses a specific verb ('Create') and resource ('item price markdown promotion'), which clearly distinguishes it from update/delete siblings. However, it does not explain what a markdown promotion is or how it differs from the sibling ebay_create_item_promotion, so an agent unfamiliar with eBay's promotion types might conflate them.
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?
The description provides no guidance on when to use this tool versus alternatives like ebay_create_item_promotion, ebay_update_item_price_markdown_promotion, or other marketing tools. There are no conditions, prerequisites, or exclusions stated, so the agent is left to infer usage purely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.