Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_campaigns

Retrieve eBay marketing campaigns using optional filters for status, name, date range, and more to monitor and optimize ad performance.

Instructions

Get campaigns through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNolimit optional endpoint parameter
offsetNooffset optional endpoint parameter
channelsNochannels optional endpoint parameter
campaignNameNocampaignName optional endpoint parameter
endDateRangeNoendDateRange optional endpoint parameter
campaignStatusNocampaignStatus optional endpoint parameter
startDateRangeNostartDateRange optional endpoint parameter
fundingStrategyNofundingStrategy optional endpoint parameter
campaignTargetingTypesNocampaignTargetingTypes optional endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.14.1
    • addedInput schema / properties / campaignName
      Added value: +{
+  "description": "campaignName optional endpoint parameter",
+  "type": "string"
+}
    • changedInput schema / properties / campaignStatus / description
      Previous value: -"Filter by campaign status: RUNNING, PAUSED, ENDED, or ARCHIVED"New value: +"campaignStatus optional endpoint parameter"
    • addedInput schema / properties / campaignTargetingTypes
      Added value: +{
+  "description": "campaignTargetingTypes optional endpoint parameter",
+  "type": "string"
+}
    • addedInput schema / properties / channels
      Added value: +{
+  "description": "channels optional endpoint parameter",
+  "type": "string"
+}
    • addedInput schema / properties / endDateRange
      Added value: +{
+  "description": "endDateRange optional endpoint parameter",
+  "type": "string"
+}
    • addedInput schema / properties / fundingStrategy
      Added value: +{
+  "description": "fundingStrategy optional endpoint parameter",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"limit optional endpoint parameter"
    • removedInput schema / properties / marketplaceId
      Removed value: -{
-  "description": "Filter by 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"
-}
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip"New value: +"offset optional endpoint parameter"
    • addedInput schema / properties / startDateRange
      Added value: +{
+  "description": "startDateRange optional endpoint parameter",
+  "type": "string"
+}
  2. First observedv1.8.10

TDQS

C2.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It only says 'Get campaigns' without mentioning side effects, authentication, rate limits, or pagination. Minimal behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one sentence but under-specified. It lacks substance and does not earn its place by providing useful information beyond the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters, no output schema, and many sibling tools, the description is far from complete. No information on return values, pagination, or how to effectively use the parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but parameter descriptions are generic ('limit optional endpoint parameter'), adding no meaning beyond the schema. The tool description does not explain any parameters or their usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get campaigns' which indicates the verb and resource, but it does not differentiate from sibling tools like ebay_get_campaign (singular) or ebay_get_campaign_by_name. It lacks specificity about what kind of campaigns or the scope of results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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 other campaign retrieval tools. No context on prerequisites, exclusions, or alternatives is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools