What it does
What came in across every conversation, in one list — the fastest way for an agent to notice a reply.
This tool drives a real LinkedIn account
Arguments
| Name | Type | Required | Meaning |
|---|---|---|---|
| limit | number | no | 1–250 (default 30) |
| cursor | string | no | The `cursor` from the previous page, to continue |
| account | string | no | Sender account id or name to act as. Defaults to the healthiest connected account. |
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:
{
"type": "object",
"properties": {
"limit": {
"type": "number",
"description": "1–250 (default 30)"
},
"cursor": {
"type": "string",
"description": "The `cursor` from the previous page, to continue"
},
"account": {
"type": "string",
"description": "Sender account id or name to act as. Defaults to the healthiest connected account."
}
}
}Request
Paste this, swap the key, and you have called the tool.
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": "list_recent_messages",
"arguments": { "limit": 30 }
}
}'Returns
{ account, count, cursor, messages: [{ id, conversationId, text, at, fromMe, senderProviderId, type }] }
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.
{ "account": "Marcus Feld", "count": 1, "cursor": "…", "messages": [{ "id": "7Hq…", "conversationId": "1lb3…", "text": "Sounds interesting", "at": 1790000000000, "fromMe": false, "senderProviderId": "ACoAAB1x…", "type": "MESSAGE" }] }Rate limit
30 LinkedIn tool calls per 5 minutes, per workspace. Exceeding it returns HTTP 429 with JSON-RPC error -32002 and a Retry-After header. The budget is shared by every LinkedIn tool and counted per workspace, so minting a second key does not buy a second allowance.
The limit exists because an agent retrying in a loop is the request pattern that gets a LinkedIn account restricted, and a restricted account is a much worse outcome for you than a 429. Workspace tools do not spend this budget.
Related tools
get_conversation
One LinkedIn conversation: who is in it (headline, degree) and its messages, oldest first
propose_reply
Propose a reply in an existing LinkedIn conversation. NOT sent: it waits in Approvals.
All 65 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.