Create ads for eBay inventory items by providing their reference ID and type. Set bid percentage and assign to a campaign to start promoting products.
Create ads by inventory reference through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Create ads by inventory reference request body | |
| campaignId | Yes | campaignId required endpoint parameter |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / adsRemoved value: -{
- "additionalProperties": false,
- "description": "Ad creation request",
- "properties": {
- "bidPercentage": {
- "description": "Bid percentage for all ads",
- "type": "string"
- },
- "inventoryReferences": {
- "description": "Array of inventory references",
- "items": {
- "additionalProperties": false,
- "properties": {
- "inventoryReferenceId": {
- "description": "SKU or inventory item group key",
- "type": "string"
- },
- "inventoryReferenceType": {
- "description": "Reference type",
- "enum": [
- "INVENTORY_ITEM",
- "INVENTORY_ITEM_GROUP"
- ],
- "type": "string"
- }
- },
- "required": [
- "inventoryReferenceId",
- "inventoryReferenceType"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "inventoryReferences"
- ],
- "type": "object"
-}Input schema / properties / campaignId / descriptionPrevious value: -"Campaign ID"New value: +"campaignId required endpoint parameter"Input schema / properties / requestAdded value: +{
+ "additionalProperties": false,
+ "description": "Create ads by inventory reference request body",
+ "properties": {
+ "bidPercentage": {
+ "type": "string"
+ },
+ "inventoryReferenceId": {
+ "type": "string"
+ },
+ "inventoryReferenceType": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Input schema / requiredPrevious value: -[
- "campaignId",
- "ads"
-]New value: +[
+ "campaignId",
+ "request"
+]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only provide readOnlyHint=false, which signals a write operation. The description adds no behavioral context beyond that: no mention of side effects, required permissions, rate limits, or what happens to existing ads. For a mutation tool, this is a significant gap.
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, efficient sentence that conveys the core action and resource. It's appropriately sized, though it could be more informative 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?
For a mutation tool with no output schema and minimal annotations, the description is thin. It doesn't explain the request body structure, the meaning of bidPercentage, or how this differs from the bulk variant. An agent would need to open the schema and infer a lot.
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%, so the schema already documents both parameters. The description adds no additional meaning beyond what the schema provides, so the baseline 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 states a specific verb ('Create') and resource ('ads by inventory reference') through the eBay Marketing API. It clearly distinguishes from sibling tools like ebay_create_ad_by_listing_id and ebay_bulk_create_ads_by_inventory_reference, though it doesn't explicitly name 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 implies usage context by naming the API and the resource type, but it doesn't explicitly state when to use this tool versus alternatives like ebay_bulk_create_ads_by_inventory_reference or ebay_create_ad_by_listing_id. An agent would need to infer the distinction from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.