ebay-mcp

ebay_create_payment_policy

Create a payment policy for eBay listings. Define payment methods, deposits, and full payment due dates to set clear buyer terms.

Instructions

Create a new payment policy

Input Schema

TableJSON Schema

Name	Required	Description	Default
`policy`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv1.14.1Jul 22, 2026

changedInput schema / properties / policy / additionalProperties
```
Previous value: -trueNew value: +false
```
removedInput schema / properties / policy / description
```
Removed value: -"Payment policy details"
```
changedInput schema / properties / policy / properties / categoryTypes / items / additionalProperties
```
Previous value: -trueNew value: +false
```
changedInput schema / properties / policy / properties / deposit / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / policy / properties / deposit / properties / amount

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "currency": {
+      "type": "string"
+    },
+    "value": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedInput schema / properties / policy / properties / deposit / properties / depositAmount

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "currency": {
-      "type": "string"
-    },
-    "value": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "currency",
-    "value"
-  ],
-  "type": "object"
-}

removedInput schema / properties / policy / properties / deposit / properties / depositType

Removed value: -{
-  "enum": [
-    "PERCENTAGE",
-    "FIXED_AMOUNT"
-  ],
-  "type": "string"
-}

changedInput schema / properties / policy / properties / deposit / properties / dueIn / additionalProperties
```
Previous value: -trueNew value: +false
```
removedInput schema / properties / policy / properties / deposit / properties / dueIn / required
```
Removed value: -[
-  "unit",
-  "value"
-]
```

addedInput schema / properties / policy / properties / deposit / properties / paymentMethods

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "brands": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "paymentMethodType": {
+        "type": "string"
+      },
+      "recipientAccountReference": {
+        "additionalProperties": false,
+        "properties": {
+          "referenceId": {
+            "type": "string"
+          },
+          "referenceType": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / policy / properties / marketplaceId / enum

Added 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"
+]

addedInput schema / properties / policy / properties / paymentMethods / items / $ref

Added value: +"#/properties/policy/properties/deposit/properties/paymentMethods/items"

removedInput schema / properties / policy / properties / paymentMethods / items / additionalProperties
```
Removed value: -true
```

removedInput schema / properties / policy / properties / paymentMethods / items / properties

Removed value: -{
-  "brands": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "paymentMethodType": {
-    "type": "string"
-  },
-  "recipientAccountReference": {
-    "additionalProperties": true,
-    "properties": {
-      "referenceId": {
-        "type": "string"
-      },
-      "referenceType": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-}

removedInput schema / properties / policy / properties / paymentMethods / items / required
```
Removed value: -[
-  "paymentMethodType"
-]
```
removedInput schema / properties / policy / properties / paymentMethods / items / type
```
Removed value: -"object"
```

First observedv1.8.10May 31, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Without annotations, the description carries the burden. It only states 'Create', implying a mutation, but no details on side effects, auth requirements, or expected behavior. No output schema provided.

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?

Although brief (7 words), it is underspecified and does not earn its place. It could be expanded to include key details without sacrificing conciseness.

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 the complex nested input schema, lack of annotations, and no output schema, the description is completely inadequate. It fails to provide essential context for effective tool invocation.

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

Parameters1/5

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

With 0% schema description coverage, the description must explain parameters. It does not describe the complex 'policy' object or its nested fields at all, leaving the agent with no understanding of what to provide.

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

Purpose4/5

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

The description clearly states the verb 'Create' and the resource 'payment policy', distinguishing it from sibling tools like get, update, delete. However, it lacks context on what a payment policy is or its scope (e.g., eBay listings).

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 on when to use this tool versus alternatives, no prerequisites or context provided. The description is purely functional without any decision-making support.

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

Deploy Server

ebay_create_payment_policy

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools