Tool reference · Workspace

get_inbox

Get unified inbox conversations

read-onlyreads the workspacenot rate limited

Updated 2026-09-18 · Server 2.0.0

What it does

The unified inbox: one thread per lead across every sender account. This is the tool behind "summarise what came in today".

Arguments

None. Send an empty arguments object.

This table is generated from the literal inputSchema that tools/list returns, so what your client sees and what this page says are the same object:

inputSchema
{
  "type": "object",
  "properties": {}
}

Request

Paste this, swap the key, and you have called the tool.

curl
curl -s https://topclozer.com/api/mcp \
  -H "Authorization: Bearer tcz_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "get_inbox",
      "arguments": { }
    }
  }'

Returns

An array of conversations: id, senderAccountId, leadId, unread, favorite, updatedAt (epoch ms), messages[], and — when the reply has been classified — intent and hot.

The payload arrives inside an MCP content block — one text block whose body is this JSON, pretty-printed. Parse the string; there is no structured-content field.

payload
[
  {
    "id": "cnv_51ab",
    "senderAccountId": "snd_02",
    "leadId": "led_88b1",
    "unread": true,
    "favorite": false,
    "updatedAt": 1789084800000,
    "intent": "meeting",
    "hot": true,
    "messages": [
      { "id": "msg_1", "direction": "out", "body": "…", "aiGenerated": true, "status": "sent", "createdAt": "2026-09-02" },
      { "id": "msg_2", "direction": "in",  "body": "Happy to chat Thursday.", "aiGenerated": false, "status": "sent", "createdAt": "2026-09-03" }
    ]
  }
]

Worth knowing

intent is one of meeting, interested, question, objection, not_now, not_interested, neutral, and is absent until the message has been classified. Messages are returned in full — there is no since/limit argument.

Limits

No request limit. This tool reads the workspace database and costs nothing to serve. The limits that bite in this product are the sending controls — per-sender weekly invite caps, the warm-up ramp, the working-hours window and a randomised gap between actions — and no tool can raise them.

Related tools

All 21 tools are listed on the tool index. Connecting a client is on the Claude setup page, and the protocol details are on the server page.