Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_contest_payment_dispute

Submit evidence to contest an eBay payment dispute when you disagree with a buyer's claim.

Instructions

Contest a payment dispute by providing evidence. Use this when you disagree with the buyer claim and want to provide proof.

Required OAuth Scope: sell.fulfillment Minimum Scope: https://api.ebay.com/oauth/api_scope/sell.fulfillment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoGenerated contestPaymentDispute request body
paymentDisputeIdYesThe unique payment dispute ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.14.1
    • addedInput schema / properties / body
      Added value: +{
+  "additionalProperties": false,
+  "description": "Generated contestPaymentDispute request body",
+  "properties": {
+    "note": {
+      "description": "Seller note for contesting the dispute",
+      "maxLength": 1000,
+      "type": "string"
+    },
+    "returnAddress": {
+      "additionalProperties": false,
+      "description": "Return address for the buyer",
+      "properties": {
+        "addressLine1": {
+          "description": "Street address line 1",
+          "type": "string"
+        },
+        "addressLine2": {
+          "description": "Street address line 2",
+          "type": "string"
+        },
+        "city": {
+          "description": "City name",
+          "type": "string"
+        },
+        "country": {
+          "description": "Two-letter ISO 3166-1 country code",
+          "type": "string"
+        },
+        "county": {
+          "description": "County name",
+          "type": "string"
+        },
+        "fullName": {
+          "description": "Full name of the return address owner",
+          "type": "string"
+        },
+        "postalCode": {
+          "description": "Postal or ZIP code",
+          "type": "string"
+        },
+        "primaryPhone": {
+          "additionalProperties": false,
+          "description": "Primary phone number for the return address",
+          "properties": {
+            "countryCode": {
+              "description": "Two-letter ISO 3166-1 country code",
+              "type": "string"
+            },
+            "number": {
+              "description": "Primary phone number",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "stateOrProvince": {
+          "description": "State or province",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "revision": {
+      "description": "Payment dispute revision number",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / properties / paymentDisputeId / description
      Previous value: -"The payment dispute ID to contest"New value: +"The unique payment dispute ID"
    • removedInput schema / properties / returnAddress
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Return address for item returns (if applicable)",
-  "properties": {
-    "addressLine1": {
-      "type": "string"
-    },
-    "addressLine2": {
-      "type": "string"
-    },
-    "city": {
-      "type": "string"
-    },
-    "countryCode": {
-      "description": "Two-letter ISO 3166-1 country code",
-      "type": "string"
-    },
-    "postalCode": {
-      "type": "string"
-    },
-    "stateOrProvince": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "countryCode"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / revisionNumber
      Removed value: -{
-  "description": "Dispute revision number",
-  "type": "number"
-}
  2. First observedv1.8.10

TDQS

A3.8/5.0
Behavior3/5

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

Annotations are absent, so the description carries the burden. It specifies OAuth scopes required, which is helpful. However, it does not disclose behavioral traits such as whether the action is synchronous, side effects, or expected response. Partial coverage.

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 concise with two sentences plus OAuth scope. It is well-structured and front-loaded with purpose. No wasted words.

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

Completeness3/5

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

For a simple action with 2 parameters and no output schema, the description covers the essential 'when' and OAuth. However, it lacks details on what happens after contesting, expected response, or prerequisites beyond OAuth. Slightly incomplete.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions. It does not elaborate on how to use parameters effectively (e.g., how to obtain revision number).

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

Purpose5/5

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

The description clearly states the action ('Contest a payment dispute by providing evidence') and when to use it ('when you disagree with the buyer claim'). It distinguishes from sibling tools like ebay_accept_payment_dispute and ebay_get_payment_dispute.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use ('when you disagree with the buyer claim and want to provide proof'). It implies when not to use (if agreeing, use accept_payment_dispute). However, it lacks explicit alternatives or exclusions.

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