ebay-mcp

ebay_get_conversations

Retrieve eBay buyer-seller conversations with filters for type, status, time, user, and listing reference. Pagination allows access to full conversation history.

Instructions

Get all buyer-seller conversations (paginated)

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of items to return (25-50)
`offset`	No	Number of items to skip
`endTime`	No	End time for retrieving conversations (ISO 8601 format)
`startTime`	No	Start time for retrieving conversations (ISO 8601 format)
`referenceId`	No	Filter by reference ID (e.g., listing ID)
`referenceType`	No	Reference type (currently only LISTING is supported)
`conversationType`	Yes	Type of conversation: FROM_EBAY or FROM_MEMBERS
`conversationStatus`	No	Filter by status: ACTIVE, ARCHIVE, DELETE, READ, UNREAD
`otherPartyUsername`	No	Filter by specific eBay user

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv1.14.1Jul 22, 2026

addedInput schema / properties / conversationStatus

Added value: +{
+  "description": "Filter by status: ACTIVE, ARCHIVE, DELETE, READ, UNREAD",
+  "type": "string"
+}

addedInput schema / properties / conversationType

Added value: +{
+  "description": "Type of conversation: FROM_EBAY or FROM_MEMBERS",
+  "type": "string"
+}

removedInput schema / properties / conversation_status

Removed value: -{
-  "description": "Filter by status: ACTIVE, ARCHIVE, DELETE, READ, UNREAD",
-  "type": "string"
-}

removedInput schema / properties / conversation_type

Removed value: -{
-  "description": "Type of conversation: FROM_EBAY or FROM_MEMBERS",
-  "type": "string"
-}

addedInput schema / properties / endTime

Added value: +{
+  "description": "End time for retrieving conversations (ISO 8601 format)",
+  "type": "string"
+}

removedInput schema / properties / end_time

Removed value: -{
-  "description": "End time for retrieving conversations (ISO 8601 format)",
-  "type": "string"
-}

addedInput schema / properties / limit / exclusiveMinimum
```
Added value: +0
```

changedInput schema / properties / limit / type

Previous value: -"string"New value: +"number"

addedInput schema / properties / offset / minimum
```
Added value: +0
```

changedInput schema / properties / offset / type

Previous value: -"string"New value: +"number"

addedInput schema / properties / otherPartyUsername

Added value: +{
+  "description": "Filter by specific eBay user",
+  "type": "string"
+}

removedInput schema / properties / other_party_username

Removed value: -{
-  "description": "Filter by specific eBay user",
-  "type": "string"
-}

addedInput schema / properties / referenceId

Added value: +{
+  "description": "Filter by reference ID (e.g., listing ID)",
+  "type": "string"
+}

addedInput schema / properties / referenceType

Added value: +{
+  "description": "Reference type (currently only LISTING is supported)",
+  "type": "string"
+}

removedInput schema / properties / reference_id

Removed value: -{
-  "description": "Filter by reference ID (e.g., listing ID)",
-  "type": "string"
-}

removedInput schema / properties / reference_type

Removed value: -{
-  "description": "Reference type (currently only LISTING is supported)",
-  "type": "string"
-}

addedInput schema / properties / startTime

Added value: +{
+  "description": "Start time for retrieving conversations (ISO 8601 format)",
+  "type": "string"
+}

removedInput schema / properties / start_time

Removed value: -{
-  "description": "Start time for retrieving conversations (ISO 8601 format)",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "conversation_type"
-]New value: +[
+  "conversationType"
+]

Changed13 schema fields changedv1.12.0Jun 18, 2026

addedInput schema / properties / conversation_status

Added value: +{
+  "description": "Filter by status: ACTIVE, ARCHIVE, DELETE, READ, UNREAD",
+  "type": "string"
+}

addedInput schema / properties / conversation_type

Added value: +{
+  "description": "Type of conversation: FROM_EBAY or FROM_MEMBERS",
+  "type": "string"
+}

addedInput schema / properties / end_time

Added value: +{
+  "description": "End time for retrieving conversations (ISO 8601 format)",
+  "type": "string"
+}

removedInput schema / properties / filter

Removed value: -{
-  "description": "Filter criteria for conversations",
-  "type": "string"
-}

changedInput schema / properties / limit / description

Previous value: -"Number of conversations to return"New value: +"Maximum number of items to return (25-50)"

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"string"

changedInput schema / properties / offset / description

Previous value: -"Number of conversations to skip"New value: +"Number of items to skip"

changedInput schema / properties / offset / type

Previous value: -"number"New value: +"string"

addedInput schema / properties / other_party_username

Added value: +{
+  "description": "Filter by specific eBay user",
+  "type": "string"
+}

addedInput schema / properties / reference_id

Added value: +{
+  "description": "Filter by reference ID (e.g., listing ID)",
+  "type": "string"
+}

addedInput schema / properties / reference_type

Added value: +{
+  "description": "Reference type (currently only LISTING is supported)",
+  "type": "string"
+}

addedInput schema / properties / start_time

Added value: +{
+  "description": "Start time for retrieving conversations (ISO 8601 format)",
+  "type": "string"
+}

addedInput schema / required

Added value: +[
+  "conversation_type"
+]

First observedv1.8.10May 31, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided; description only mentions 'paginated' but omits details like default pagination size, authentication requirements, or output structure. Full burden falls on description, which is insufficient.

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?

Extremely concise at 5 words, front-loaded with key info. However, slight trade-off with completeness; could expand slightly without losing efficiency.

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?

With 9 parameters and no output schema, the description provides minimal context. It does not explain the meaning of parameters or the nature of conversations, leaving gaps for the agent.

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 each parameter has a description. The tool description adds no additional meaning beyond the schema, so 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 uses specific verb 'Get' and identifies resource 'buyer-seller conversations', clearly distinguishing from sibling 'ebay_get_conversation' (singular). The term 'paginated' adds useful scope.

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 vs. alternatives like ebay_get_conversation or other retrieval tools. Lacks context for selection among many sibling tools.

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

Deploy Server

ebay_get_conversations

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools