Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

ebay_send_message

Send direct messages to eBay buyers regarding orders and inquiries. Use to answer questions, resolve issues, or provide transaction updates.

Instructions

Send a direct message to a buyer regarding a specific transaction or inquiry. Use this to communicate about orders, answer questions, resolve issues, or provide updates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
referenceNoReference to associate with the conversation
messageTextNoThe text of the message (max 2000 characters)
messageMediaNoArray of up to 5 media attachments
conversationIdNoID of existing conversation (required if sending in existing conversation)
emailCopyToSenderNoWhether to email a copy to the sender
otherPartyUsernameNoeBay username to send message to (required for new conversations)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed14 schema fields changedv1.14.1
    • addedInput schema / properties / conversationId
      Added value: +{
+  "description": "ID of existing conversation (required if sending in existing conversation)",
+  "type": "string"
+}
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "description": "ID of existing conversation (required if sending in existing conversation)",
-  "type": "string"
-}
    • addedInput schema / properties / emailCopyToSender
      Added value: +{
+  "description": "Whether to email a copy to the sender",
+  "type": "boolean"
+}
    • removedInput schema / properties / email_copy_to_sender
      Removed value: -{
-  "description": "Whether to email a copy to the sender",
-  "type": "boolean"
-}
    • addedInput schema / properties / messageMedia
      Added value: +{
+  "description": "Array of up to 5 media attachments",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "mediaName": {
+        "description": "Name of the media",
+        "type": "string"
+      },
+      "mediaType": {
+        "description": "Type of media: IMAGE, PDF, DOC, TXT",
+        "type": "string"
+      },
+      "mediaUrl": {
+        "description": "HTTPS URL of the self-hosted media",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "maxItems": 5,
+  "type": "array"
+}
    • addedInput schema / properties / messageText
      Added value: +{
+  "description": "The text of the message (max 2000 characters)",
+  "maxLength": 2000,
+  "type": "string"
+}
    • removedInput schema / properties / message_media
      Removed value: -{
-  "description": "Array of up to 5 media attachments",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "media_name": {
-        "description": "Name of the media",
-        "type": "string"
-      },
-      "media_type": {
-        "description": "Type of media: IMAGE, PDF, DOC, TXT",
-        "type": "string"
-      },
-      "media_url": {
-        "description": "HTTPS URL of the self-hosted media",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "maxItems": 5,
-  "type": "array"
-}
    • removedInput schema / properties / message_text
      Removed value: -{
-  "description": "The text of the message (max 2000 characters)",
-  "maxLength": 2000,
-  "type": "string"
-}
    • addedInput schema / properties / otherPartyUsername
      Added value: +{
+  "description": "eBay username to send message to (required for new conversations)",
+  "type": "string"
+}
    • removedInput schema / properties / other_party_username
      Removed value: -{
-  "description": "eBay username to send message to (required for new conversations)",
-  "type": "string"
-}
    • addedInput schema / properties / reference / properties / referenceId
      Added value: +{
+  "description": "The reference ID (e.g., item ID for LISTING)",
+  "type": "string"
+}
    • addedInput schema / properties / reference / properties / referenceType
      Added value: +{
+  "description": "The reference type (currently only LISTING is supported)",
+  "type": "string"
+}
    • removedInput schema / properties / reference / properties / reference_id
      Removed value: -{
-  "description": "The reference ID (e.g., item ID for LISTING)",
-  "type": "string"
-}
    • removedInput schema / properties / reference / properties / reference_type
      Removed value: -{
-  "description": "The reference type (currently only LISTING is supported)",
-  "type": "string"
-}
  2. Changed8 schema fields changedv1.12.0
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "ID of existing conversation (required if sending in existing conversation)",
+  "type": "string"
+}
    • addedInput schema / properties / email_copy_to_sender
      Added value: +{
+  "description": "Whether to email a copy to the sender",
+  "type": "boolean"
+}
    • removedInput schema / properties / messageData
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Message details including recipient and content. Must include messageText (required), and either conversationId (for replies) OR otherPartyUsername (for new messages).",
-  "properties": {
-    "conversationId": {
-      "description": "Optional conversation ID to reply to an existing thread. Use getConversations to retrieve conversation IDs. Required if replying to existing conversation.",
-      "type": "string"
-    },
-    "emailCopyToSender": {
-      "description": "If true, a copy of the message will be emailed to the sender.",
-      "type": "boolean"
-    },
-    "messageMedia": {
-      "description": "Optional array of media attachments (max 5 per message)",
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "mediaType": {
-            "description": "MIME type of the media (e.g., \"image/jpeg\")",
-            "type": "string"
-          },
-          "mediaUrl": {
-            "description": "URL of the media to attach",
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "messageText": {
-      "description": "REQUIRED. The text of the message to send (max 2000 characters).",
-      "type": "string"
-    },
-    "otherPartyUsername": {
-      "description": "eBay username of the other party (buyer or seller). Required when starting a new conversation.",
-      "type": "string"
-    },
-    "reference": {
-      "additionalProperties": false,
-      "description": "Optional reference to associate message with a listing or order.",
-      "properties": {
-        "referenceId": {
-          "description": "The ID of the listing or order to reference (e.g., item ID or order ID)",
-          "type": "string"
-        },
-        "referenceType": {
-          "description": "Type of reference. Valid values: \"LISTING\" (for item listings) or \"ORDER\" (for orders)",
-          "type": "string"
-        }
-      },
-      "type": "object"
-    }
-  },
-  "required": [
-    "messageText"
-  ],
-  "type": "object"
-}
    • addedInput schema / properties / message_media
      Added value: +{
+  "description": "Array of up to 5 media attachments",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "media_name": {
+        "description": "Name of the media",
+        "type": "string"
+      },
+      "media_type": {
+        "description": "Type of media: IMAGE, PDF, DOC, TXT",
+        "type": "string"
+      },
+      "media_url": {
+        "description": "HTTPS URL of the self-hosted media",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "maxItems": 5,
+  "type": "array"
+}
    • addedInput schema / properties / message_text
      Added value: +{
+  "description": "The text of the message (max 2000 characters)",
+  "maxLength": 2000,
+  "type": "string"
+}
    • addedInput schema / properties / other_party_username
      Added value: +{
+  "description": "eBay username to send message to (required for new conversations)",
+  "type": "string"
+}
    • addedInput schema / properties / reference
      Added value: +{
+  "additionalProperties": false,
+  "description": "Reference to associate with the conversation",
+  "properties": {
+    "reference_id": {
+      "description": "The reference ID (e.g., item ID for LISTING)",
+      "type": "string"
+    },
+    "reference_type": {
+      "description": "The reference type (currently only LISTING is supported)",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / required
      Removed value: -[
-  "messageData"
-]
  3. First observedv1.8.10

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It fails to mention important traits: that it can start new conversations or reply to existing ones, any prerequisites (e.g., authentication), rate limits, or that messages are sent immediately. The description is too brief to ensure the agent understands side effects or constraints.

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 two sentences, no extraneous words, and front-loads the primary action. Every sentence adds value, achieving maximum efficiency.

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?

Given 6 parameters (some conditionally required), no output schema, and the need to distinguish between new and existing conversations, the description is insufficiently complete. It does not explain parameter interdependence or media attachment capabilities, leaving the agent with gaps despite good schema coverage.

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 coverage is 100%, so baseline is 3. The description adds no extra parameter semantics beyond what the schema already provides. It does not clarify conditional parameter relationships (e.g., conversationId vs. otherPartyUsername) or usage patterns, so it does not enhance understanding.

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 ('Send a direct message'), the recipient ('to a buyer'), and the context ('regarding a specific transaction or inquiry'). It enumerates specific use cases (orders, questions, issues, updates), making the purpose distinct from sibling communication tools like getting conversations or leaving feedback.

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 clear when-to-use guidance: 'communicate about orders, answer questions, resolve issues, or provide updates.' However, it does not explicitly state when not to use this tool or mention alternative tools (e.g., ebay_get_conversations for reading messages), leaving some ambiguity for the agent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YosefHayim/ebay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server