Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_respond_to_feedback

Respond to buyer feedback on eBay by sending a reply or follow-up message using the feedback ID and response text.

Instructions

Respond to feedback received from a buyer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedbackIdNoThe unique identifier of the feedback being responded to
responseTextNoThe text content of the response (max 500 characters)
responseTypeNoThe type of response: REPLY or FOLLOW_UP
recipientUserIdNoThe user ID of the feedback provider

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.14.1
    • addedInput schema / properties / feedbackId
      Added value: +{
+  "description": "The unique identifier of the feedback being responded to",
+  "type": "string"
+}
    • removedInput schema / properties / feedback_id
      Removed value: -{
-  "description": "The feedback ID being responded to",
-  "type": "string"
-}
    • addedInput schema / properties / recipientUserId
      Added value: +{
+  "description": "The user ID of the feedback provider",
+  "type": "string"
+}
    • removedInput schema / properties / recipient_user_id
      Removed value: -{
-  "description": "The user ID of the feedback provider",
-  "type": "string"
-}
    • addedInput schema / properties / responseText
      Added value: +{
+  "description": "The text content of the response (max 500 characters)",
+  "maxLength": 500,
+  "type": "string"
+}
    • addedInput schema / properties / responseType
      Added value: +{
+  "description": "The type of response: REPLY or FOLLOW_UP",
+  "type": "string"
+}
    • removedInput schema / properties / response_text
      Removed value: -{
-  "description": "The response text content (max 500 characters)",
-  "type": "string"
-}
    • removedInput schema / properties / response_type
      Removed value: -{
-  "description": "The response type: REPLY or FOLLOW_UP",
-  "type": "string"
-}
  2. First observedv1.8.10

TDQS

A3.5/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 states the tool responds to feedback (a write operation) but does not mention side effects, whether it overwrites existing responses, or any permissions required. This is minimal disclosure.

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

Conciseness5/5

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

The description is a single sentence that conveys the core purpose without any wasted words. It is front-loaded and efficient.

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?

The description is brief and covers the basic purpose. However, it lacks information about return values (no output schema), does not specify that some parameters might be required (despite schema showing 0 required), and no examples or constraints beyond what is in the schema. For a straightforward tool, this is adequate but not rich.

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 descriptions cover all 4 parameters (100% coverage), so the description does not need to repeat them. The description adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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?

Description clearly states the action ('Respond'), the resource ('feedback'), and specifies it is for feedback from a buyer. This distinguishes it from sibling tools like ebay_leave_feedback_for_buyer (leaving new feedback) and ebay_get_feedback (retrieving feedback).

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

Usage Guidelines3/5

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

Description implies usage when a buyer has given feedback, but does not provide explicit guidance on when to use this tool versus alternatives like ebay_leave_feedback_for_buyer or ebay_get_feedback. No exclusions or context are provided.

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