ebay-mcp

ebay_leave_feedback_for_buyer

Leave feedback for a buyer after an eBay transaction. Provide the order line item ID, choose POSITIVE, NEUTRAL, or NEGATIVE, and add a comment to rate the buyer's experience.

Instructions

Leave feedback for a buyer. Provide orderLineItemId, commentType (POSITIVE/NEUTRAL/NEGATIVE), and commentText.

Input Schema

TableJSON Schema

Name	Required	Description
`images`	No	Array of up to 5 images
`listingId`	No	The listing ID related to the transaction
`commentText`	No	The feedback comment text (max 500 characters)
`commentType`	No	Overall rating: POSITIVE, NEUTRAL, or NEGATIVE
`sellerRatings`	No	Array of seller performance ratings
`transactionId`	No	The unique identifier of the transaction
`orderLineItemId`	No	The unique identifier of the line item

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.14.1Jul 22, 2026

addedInput schema / properties / commentText

Added value: +{
+  "description": "The feedback comment text (max 500 characters)",
+  "maxLength": 500,
+  "type": "string"
+}

addedInput schema / properties / commentType

Added value: +{
+  "description": "Overall rating: POSITIVE, NEUTRAL, or NEGATIVE",
+  "type": "string"
+}

removedInput schema / properties / comment_text

Removed value: -{
-  "description": "The feedback comment text (max 500 characters)",
-  "maxLength": 500,
-  "type": "string"
-}

removedInput schema / properties / comment_type

Removed value: -{
-  "description": "Overall rating: POSITIVE, NEUTRAL, or NEGATIVE",
-  "type": "string"
-}

addedInput schema / properties / listingId

Added value: +{
+  "description": "The listing ID related to the transaction",
+  "type": "string"
+}

removedInput schema / properties / listing_id

Removed value: -{
-  "description": "The listing ID related to the transaction",
-  "type": "string"
-}

addedInput schema / properties / orderLineItemId

Added value: +{
+  "description": "The unique identifier of the line item",
+  "type": "string"
+}

removedInput schema / properties / order_line_item_id

Removed value: -{
-  "description": "The unique identifier of the line item",
-  "type": "string"
-}

addedInput schema / properties / sellerRatings

Added value: +{
+  "description": "Array of seller performance ratings",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "key": {
+        "description": "Rating category (e.g., ON_TIME_DELIVERY, ITEM_AS_DESCRIBED)",
+        "type": "string"
+      },
+      "value": {
+        "description": "Rating value (1-5)",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedInput schema / properties / seller_ratings

Removed value: -{
-  "description": "Array of seller performance ratings",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "key": {
-        "description": "Rating category (e.g., ON_TIME_DELIVERY, ITEM_AS_DESCRIBED)",
-        "type": "string"
-      },
-      "value": {
-        "description": "Rating value (1-5)",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

addedInput schema / properties / transactionId

Added value: +{
+  "description": "The unique identifier of the transaction",
+  "type": "string"
+}

removedInput schema / properties / transaction_id

Removed value: -{
-  "description": "The unique identifier of the transaction",
-  "type": "string"
-}

Changed9 schema fields changedv1.12.0Jun 18, 2026

addedInput schema / properties / comment_text

Added value: +{
+  "description": "The feedback comment text (max 500 characters)",
+  "maxLength": 500,
+  "type": "string"
+}

addedInput schema / properties / comment_type

Added value: +{
+  "description": "Overall rating: POSITIVE, NEUTRAL, or NEGATIVE",
+  "type": "string"
+}

removedInput schema / properties / feedbackData

Removed value: -{
-  "additionalProperties": true,
-  "description": "Feedback details including rating and comment",
-  "properties": {
-    "feedbackText": {
-      "type": "string"
-    },
-    "orderLineItemId": {
-      "type": "string"
-    },
-    "rating": {
-      "enum": [
-        "POSITIVE",
-        "NEUTRAL",
-        "NEGATIVE"
-      ],
-      "type": "string"
-    }
-  },
-  "required": [
-    "orderLineItemId",
-    "rating"
-  ],
-  "type": "object"
-}

addedInput schema / properties / images

Added value: +{
+  "description": "Array of up to 5 images",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "url": {
+        "description": "URL of the image",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "maxItems": 5,
+  "type": "array"
+}

addedInput schema / properties / listing_id

Added value: +{
+  "description": "The listing ID related to the transaction",
+  "type": "string"
+}

addedInput schema / properties / order_line_item_id

Added value: +{
+  "description": "The unique identifier of the line item",
+  "type": "string"
+}

addedInput schema / properties / seller_ratings

Added value: +{
+  "description": "Array of seller performance ratings",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "key": {
+        "description": "Rating category (e.g., ON_TIME_DELIVERY, ITEM_AS_DESCRIBED)",
+        "type": "string"
+      },
+      "value": {
+        "description": "Rating value (1-5)",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / transaction_id

Added value: +{
+  "description": "The unique identifier of the transaction",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "feedbackData"
-]
```

First observedv1.8.10May 31, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions leaving feedback but fails to disclose that the operation is likely irreversible, that it may affect buyer-seller ratings, or that it requires authentication. Additionally, it omits four parameters (images, listingId, sellerRatings, transactionId) from the behavioral description.

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 very short (one sentence) and front-loaded with the primary action. It is concise and to the point. However, it omits important information about other parameters, which could be considered too brief for a tool with 7 parameters.

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?

Given that there are 7 parameters and no output schema or annotations, the description is incomplete. It only addresses 3 of 7 parameters, leaving the purpose of images, listingId, sellerRatings, and transactionId unexplained. The agent cannot determine which parameters are mandatory or how they relate to the feedback action.

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 each parameter has a description in the schema. The description lists three key parameters (orderLineItemId, commentType, commentText) but adds no additional meaning beyond what the schema already provides. It does not explain the relationship between parameters or provide formatting details.

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 tool's purpose: 'Leave feedback for a buyer.' It identifies the verb (leave) and resource (feedback for a buyer). However, it does not differentiate from sibling tools like ebay_respond_to_feedback, which is for responding to received feedback, not leaving new feedback.

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?

The description provides minimal guidance by listing three parameters to provide but does not explain when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context such as when feedback should be left (e.g., after a transaction).

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

Deploy Server

ebay_leave_feedback_for_buyer

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools