Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_campaigns

Read-only

Fetch eBay marketing campaigns with filters for status, name, date ranges, and funding, enabling targeted campaign management.

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.4/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes this as a read-only operation, so the description adds no new behavioral context. It does not mention pagination behavior, response shape, defaults when no filters are supplied, or any API-specific constraints, failing to go beyond what the annotation already provides.

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

Conciseness4/5

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

The description is a single efficient sentence with no wasted words. It front-loads the verb and resource, making it easy to scan. However, its brevity is achieved by omitting important details, which slightly reduces its value as a complete description.

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

Completeness2/5

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

With no output schema, nine optional parameters, and unhelpful schema descriptions, the one-sentence description is insufficient. It does not explain the purpose of limit/offset, how filters like campaignName or campaignStatus work, or what the response contains, leaving the agent with inadequate information to invoke the tool correctly.

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?

Although schema description coverage is 100%, the schema descriptions are tautological (e.g., 'limit optional endpoint parameter') and provide no real meaning. The tool description itself says nothing about the parameters, so an agent cannot determine what values are valid, how they interact, or what each filter does.

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 a verb ('Get') and resource ('campaigns'), but it does not clarify whether this is a list/query operation or a singular fetch. It also fails to distinguish itself from sibling tools like ebay_get_campaign or ebay_get_campaign_by_name, leaving the agent uncertain about the operation's exact scope.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives (e.g., ebay_get_campaign for a single campaign) or how the filter parameters map to different use cases. The agent is left without any decision support for tool selection.

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