Create eBay advertising campaigns by specifying budget, targeting criteria, and campaign schedule through the Marketing API.
Create campaign through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Create campaign request body |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / campaignRemoved value: -{
- "additionalProperties": false,
- "description": "Campaign configuration",
- "properties": {
- "campaignName": {
- "description": "Campaign name",
- "type": "string"
- },
- "endDate": {
- "description": "Campaign end date (ISO 8601 format)",
- "type": "string"
- },
- "fundingStrategy": {
- "additionalProperties": false,
- "description": "Funding strategy configuration",
- "properties": {
- "bidPercentage": {
- "description": "Bid percentage for CPS campaigns (e.g., \"10.5\")",
- "type": "string"
- },
- "fundingModel": {
- "description": "Funding model: CPS or CPC",
- "enum": [
- "COST_PER_SALE",
- "COST_PER_CLICK"
- ],
- "type": "string"
- }
- },
- "required": [
- "fundingModel"
- ],
- "type": "object"
- },
- "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"
- },
- "startDate": {
- "description": "Campaign start date (ISO 8601 format)",
- "type": "string"
- }
- },
- "required": [
- "campaignName",
- "marketplaceId",
- "fundingStrategy"
- ],
- "type": "object"
-}Input schema / properties / requestAdded value: +{
+ "additionalProperties": false,
+ "description": "Create campaign request body",
+ "properties": {
+ "budget": {
+ "additionalProperties": false,
+ "properties": {
+ "daily": {
+ "additionalProperties": false,
+ "properties": {
+ "amount": {
+ "type": "string"
+ },
+ "currency": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+ },
+ "campaignCriterion": {
+ "additionalProperties": false,
+ "properties": {
+ "autoSelectFutureInventory": {
+ "type": "boolean"
+ },
+ "criterionType": {
+ "type": "string"
+ },
+ "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": {
+ "additionalProperties": false,
+ "properties": {
+ "currency": {
+ "type": "string"
+ },
+ "value": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "minPrice": {
+ "$ref": "#/properties/request/properties/campaignCriterion/properties/selectionRules/items/properties/maxPrice"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ },
+ "campaignName": {
+ "type": "string"
+ },
+ "channels": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "endDate": {
+ "type": "string"
+ },
+ "fundingStrategy": {
+ "additionalProperties": false,
+ "properties": {
+ "bidPercentage": {
+ "type": "string"
+ },
+ "fundingModel": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "marketplaceId": {
+ "type": "string"
+ },
+ "startDate": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "campaignName",
+ "marketplaceId",
+ "startDate"
+ ],
+ "type": "object"
+}Input schema / requiredPrevious value: -[
- "campaign"
-]New value: +[
+ "request"
+]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include only readOnlyHint: false, and the description merely restates the create action without adding behavioral context. It does not disclose idempotency, required prior setup (such as having a seller account or opted-in program), the outcome of a successful creation, or potential side effects. The description adds no transparency beyond what the annotation already implies.
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 sentence, but it is under-specified and mostly restates the tool name. 'Create campaign through the eBay Marketing API' adds only marginal context (the API family) and fails to structure important details such as required fields, campaign types, or links to additional workflows. This is under-specification, not efficient conciseness.
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 tool has a complex nested schema (budget, fundingStrategy, campaignCriterion, etc.) and a large sibling context, yet the description provides no awareness of these fields, required elements, or operational constraints. Without an output schema and with only a single generic sentence, an agent cannot determine what constitutes a valid campaign creation request or how to handle edge cases. The context is incomplete for a complex mutation operation.
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% at the top-level request parameter, which has a brief description ('Create campaign request body'). However, nested fields like campaignName, marketplaceId, and startDate have no descriptions. The tool description provides no additional parameter semantics, so it does not compensate for the inner fields, but the baseline of 3 applies due to high schema coverage.
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?
Description states a specific verb ('Create') and resource ('campaign'), so an agent knows the basic operation. However, it does not differentiate from sibling tools like ebay_setup_quick_campaign, ebay_clone_campaign, or ebay_launch_campaign, which also relate to campaign creation. It is clear at the verb+resource level but lacks sibling differentiation.
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?
There is no guidance on when to use this tool versus alternatives. The description does not mention prerequisites (e.g., opting into the advertising program), campaign types, or conditions under which the agent should choose this over ebay_setup_quick_campaign or ebay_clone_campaign. No when/when-not guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.