Set up an eBay marketing campaign through the Marketing API. Specify campaign name, marketplace, and optional settings for budget, listings, and schedule to launch promotions.
Setup quick campaign through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Setup quick campaign request body |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.14.1Input schema / properties / quickCampaignRemoved value: -{
- "additionalProperties": false,
- "description": "Quick campaign configuration",
- "properties": {
- "campaignName": {
- "description": "Campaign name",
- "type": "string"
- },
- "fundingStrategy": {
- "additionalProperties": false,
- "description": "Funding strategy",
- "properties": {
- "bidPercentage": {
- "description": "Bid percentage (e.g., \"10.5\")",
- "type": "string"
- },
- "fundingModel": {
- "description": "Funding model",
- "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"
- }
- },
- "required": [
- "campaignName",
- "marketplaceId",
- "fundingStrategy"
- ],
- "type": "object"
-}Input schema / properties / requestAdded value: +{
+ "additionalProperties": false,
+ "description": "Setup quick campaign request body",
+ "properties": {
+ "campaignName": {
+ "type": "string"
+ },
+ "dailyBudget": {
+ "additionalProperties": false,
+ "properties": {
+ "currency": {
+ "type": "string"
+ },
+ "value": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "endDate": {
+ "type": "string"
+ },
+ "fundingStrategy": {
+ "additionalProperties": false,
+ "properties": {
+ "bidPercentage": {
+ "type": "string"
+ },
+ "fundingModel": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "listingIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "marketplaceId": {
+ "type": "string"
+ },
+ "startDate": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "campaignName",
+ "marketplaceId"
+ ],
+ "type": "object"
+}Input schema / requiredPrevious value: -[
- "quickCampaign"
-]New value: +[
+ "request"
+]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavior but only says 'Setup quick campaign'. It does not mention authentication requirements, side effects (e.g., creation on eBay), idempotency, or return value. The agent lacks critical behavioral context.
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 overly brief and omits essential details. Conciseness should not come at the expense of clarity; here, the agent is left underinformed.
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?
Given no annotations, no output schema, and a nested input schema, the description is severely incomplete. It does not explain the tool's purpose in the campaign lifecycle, what constitutes a 'quick' setup, or what the tool returns (e.g., campaign ID). The agent has insufficient information to decide when and how to use this tool.
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 coverage is 100%, so baseline is 3, but the description adds no parameter-level information. It does not explain the purpose or constraints of the nested fields (e.g., campaignName, marketplaceId), leaving the agent without helpful beyond-schema context.
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 'Setup quick campaign through the eBay Marketing API' provides a vague verb and resource, but fails to clarify what distinguishes a 'quick campaign' from regular campaigns. Sibling tools like ebay_create_campaign are similar, and no differentiation is offered.
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 on when to use this tool versus alternatives like ebay_create_campaign or ebay_launch_campaign. There is no context for prerequisites, exclusions, or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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