Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_update_conversation

Update a conversation's status (ACTIVE, ARCHIVE, DELETE) or mark it as read/unread using the conversation ID.

Instructions

Update a single conversation (conversationStatus: ACTIVE, ARCHIVE, DELETE; or read flag).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
readNoThe read status to set (true = read, false = unread)
conversationIdNoThe unique identifier of the conversation
conversationTypeNoThe existing type: FROM_MEMBERS or FROM_EBAY (required but cannot be updated)
conversationStatusNoThe updated status: ACTIVE, ARCHIVE, DELETE

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.14.1
    • addedInput schema / properties / conversationId
      Added value: +{
+  "description": "The unique identifier of the conversation",
+  "type": "string"
+}
    • addedInput schema / properties / conversationStatus
      Added value: +{
+  "description": "The updated status: ACTIVE, ARCHIVE, DELETE",
+  "type": "string"
+}
    • addedInput schema / properties / conversationType
      Added value: +{
+  "description": "The existing type: FROM_MEMBERS or FROM_EBAY (required but cannot be updated)",
+  "type": "string"
+}
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "description": "The unique identifier of the conversation",
-  "type": "string"
-}
    • removedInput schema / properties / conversation_status
      Removed value: -{
-  "description": "The updated status: ACTIVE, ARCHIVE, DELETE",
-  "type": "string"
-}
    • removedInput schema / properties / conversation_type
      Removed value: -{
-  "description": "The existing type: FROM_MEMBERS or FROM_EBAY (required but cannot be updated)",
-  "type": "string"
-}
  2. Changed6 schema fields changedv1.12.0
    • changedInput schema / properties / conversation_id / description
      Previous value: -"The conversation ID"New value: +"The unique identifier of the conversation"
    • addedInput schema / properties / conversation_status
      Added value: +{
+  "description": "The updated status: ACTIVE, ARCHIVE, DELETE",
+  "type": "string"
+}
    • addedInput schema / properties / conversation_type
      Added value: +{
+  "description": "The existing type: FROM_MEMBERS or FROM_EBAY (required but cannot be updated)",
+  "type": "string"
+}
    • removedInput schema / properties / flagged
      Removed value: -{
-  "description": "Mark as flagged/unflagged",
-  "type": "boolean"
-}
    • changedInput schema / properties / read / description
      Previous value: -"Mark as read/unread"New value: +"The read status to set (true = read, false = unread)"
    • removedInput schema / required
      Removed value: -[
-  "conversation_id"
-]
  3. First observedv1.8.10

TDQS

A4/5.0
Behavior3/5

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

Discloses that it updates a conversation and lists possible status values. However, with no annotations, it fails to describe effects of DELETE, required permissions, or return behavior.

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?

Single sentence with key information, no wasted words. Could be slightly more structured but effective.

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?

Lacks description of return value or output. For a mutation tool with no output schema, this omission reduces completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds value by explaining the meaning of conversationStatus values and that conversationType is required but cannot be updated.

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 verb 'Update' and resource 'single conversation', listing allowed statuses and read flag. Distinguishes from sibling 'ebay_bulk_update_conversation' by specifying single conversation.

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?

Implies when to use by specifying the fields to update (status or read flag). Does not explicitly exclude bulk updates or provide prerequisites, but naming and context make usage clear.

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