Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_promotions

Retrieve promotions from eBay Marketing API using required marketplace ID and optional filters for type, status, and search query.

Instructions

Get promotions through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoq optional endpoint parameter
sortNosort optional endpoint parameter
limitNolimit optional endpoint parameter
offsetNooffset optional endpoint parameter
marketplaceIdYesmarketplaceId required endpoint parameter
promotionTypeNopromotionType optional endpoint parameter
promotionStatusNopromotionStatus optional endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.14.1
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"limit optional endpoint parameter"
    • changedInput schema / properties / marketplaceId / description
      Previous value: -"Filter by marketplace ID"New value: +"marketplaceId required endpoint parameter"
    • removedInput schema / properties / marketplaceId / enum
      Removed value: -[
-  "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"
-]
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip"New value: +"offset optional endpoint parameter"
    • changedInput schema / properties / promotionStatus / description
      Previous value: -"Filter by status: DRAFT, SCHEDULED, RUNNING, PAUSED, ENDED"New value: +"promotionStatus optional endpoint parameter"
    • changedInput schema / properties / promotionType / description
      Previous value: -"Filter by type: ORDER_DISCOUNT, MARKDOWN_SALE, etc."New value: +"promotionType optional endpoint parameter"
    • addedInput schema / properties / q
      Added value: +{
+  "description": "q optional endpoint parameter",
+  "type": "string"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "sort optional endpoint parameter",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "marketplaceId"
+]
  2. First observedv1.8.10

TDQS

C2/5.0
Behavior1/5

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Get promotions' with no information on side effects, required permissions, or response structure. This is insufficient for safe tool invocation.

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 it is under-specified. Conciseness should not sacrifice completeness; here, critical details are omitted.

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 7 parameters, no output schema, and no annotations, the description is severely lacking. It does not explain return values, filtering, pagination, or how to interpret results, leaving the agent blind.

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 coverage is 100%, the schema descriptions are generic (e.g., 'q optional endpoint parameter') and do not explain semantics. The tool description adds no further meaning, so it fails to compensate for vacuous parameter documentation.

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 promotions', which is a verb+resource. However, it does not differentiate from sibling tools like ebay_get_item_promotion or ebay_get_promotion_reports, which also retrieve promotion data. The phrase 'through the eBay Marketing API' is redundant and adds no specificity.

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 alternatives. There is no mention of prerequisites, filters, or exclusions, leaving the agent without context for 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