Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_feedback

Retrieve eBay feedback for a user by type, filtering by received or sent feedback. Use optional sort, limit, and filter parameters to refine results.

Instructions

Get feedback for a user by type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order for results
limitNoMaximum number of items to return per page (25-200)
filterNoFilter criteria for the query
offsetNoNumber of items to skip
userIdYesThe unique identifier (eBay username) of the user
listingIdNoFilter by listing ID
feedbackIdNoFilter by specific feedback ID
feedbackTypeYesType of feedback (FEEDBACK_RECEIVED or FEEDBACK_SENT)
transactionIdNoThe unique identifier of the transaction
orderLineItemIdNoFilter by order line item ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv1.14.1
    • addedInput schema / properties / feedbackId
      Added value: +{
+  "description": "Filter by specific feedback ID",
+  "type": "string"
+}
    • addedInput schema / properties / feedbackType
      Added value: +{
+  "description": "Type of feedback (FEEDBACK_RECEIVED or FEEDBACK_SENT)",
+  "type": "string"
+}
    • removedInput schema / properties / feedback_id
      Removed value: -{
-  "description": "Filter by specific feedback ID",
-  "type": "string"
-}
    • removedInput schema / properties / feedback_type
      Removed value: -{
-  "description": "Type: FEEDBACK_RECEIVED or FEEDBACK_SENT",
-  "type": "string"
-}
    • changedInput schema / properties / filter / description
      Previous value: -"Filter criteria"New value: +"Filter criteria for the query"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of feedback items to return"New value: +"Maximum number of items to return per page (25-200)"
    • addedInput schema / properties / limit / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / limit / type
      Previous value: -"string"New value: +"number"
    • addedInput schema / properties / listingId
      Added value: +{
+  "description": "Filter by listing ID",
+  "type": "string"
+}
    • removedInput schema / properties / listing_id
      Removed value: -{
-  "description": "Filter by listing ID",
-  "type": "string"
-}
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"string"New value: +"number"
    • addedInput schema / properties / orderLineItemId
      Added value: +{
+  "description": "Filter by order line item ID",
+  "type": "string"
+}
    • removedInput schema / properties / order_line_item_id
      Removed value: -{
-  "description": "Filter by order line item ID",
-  "type": "string"
-}
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order"New value: +"Sort order for results"
    • addedInput schema / properties / transactionId
      Added value: +{
+  "description": "The unique identifier of the transaction",
+  "type": "string"
+}
    • removedInput schema / properties / transaction_id
      Removed value: -{
-  "description": "Filter by transaction ID",
-  "type": "string"
-}
    • addedInput schema / properties / userId
      Added value: +{
+  "description": "The unique identifier (eBay username) of the user",
+  "type": "string"
+}
    • removedInput schema / properties / user_id
      Removed value: -{
-  "description": "The eBay username of the user",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "user_id",
-  "feedback_type"
-]New value: +[
+  "userId",
+  "feedbackType"
+]
  2. First observedv1.8.10

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'get feedback', lacking details on whether this is a read-only operation, what the response format is, or any side effects. The schema parameters imply filtering but the description does not explain behavior beyond the basic action.

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 a single short sentence, which is efficient and front-loaded. It could benefit from a bit more detail, but it avoids verbosity and gets the core purpose across.

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 no output schema and no annotations, the description is insufficient. It does not explain return structure, pagination (sort/limit/offset), or how to use the many optional filters. The long list of sibling feedback tools further highlights the need for more context to aid selection.

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 the schema already explains all 10 parameters. The description adds minimal value by mentioning 'by type', which loosely ties to the feedbackType parameter, but does not provide additional meaning beyond what's in the schema.

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 'Get feedback for a user by type', specifying the verb (get), resource (feedback), and key filter (by user and type). This distinguishes it from sibling tools like 'leave_feedback_for_buyer' or 'respond_to_feedback', which are write operations.

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 like ebay_get_awaiting_feedback or ebay_get_feedback_rating_summary. Does not mention prerequisites, required authentication, or typical use cases.

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