Get conversation
One conversation with its customer, status, assignee, tags and every thread, notes included.
MCP tool help_scout_read → get_conversation
read
Returns the conversation as the thread view shows it: customer, inbox, status, assignee, tags and each thread in order, marked as customer message, reply or internal note. Attachments come back as names, not files. Use it before replying so you do not repeat what a note or a teammate already said.
Parameters
| Name | Type | Description |
|---|---|---|
| conversation_id integer required | integer | Conversation number from search_conversations. |
tools/call
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "help_scout_read",
"arguments": {
"operation": "get_conversation",
"arguments": {
"conversation_id": 1
}
}
}
}Example response
{
"content": [
{
"type": "text",
"text": "{ ... same JSON as structuredContent ... }"
}
],
"structuredContent": {
"conversation_id": 48244,
"subject": "Charged twice in October",
"status": "active",
"assignee": null,
"tags": [
"billing"
],
"customer": {
"name": "Priya Nair",
"email": "priya@example.com"
},
"inbox": "Support",
"threads": [
{
"type": "customer",
"author": "Priya Nair",
"created_at": "2026-10-16T07:55:00Z",
"text": "Hi, my card was charged twice on 1 October. Can you check?"
},
{
"type": "note",
"author": "Maria Silva",
"created_at": "2026-10-16T08:12:00Z",
"text": "Looking at the invoices now."
}
]
},
"isError": false
}