What it does
One workspace-wide roll-up. Cheapest way for an agent to answer "how is outreach going" without walking every campaign.
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:
{
"type": "object",
"properties": {}
}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": "get_stats",
"arguments": { }
}
}'Returns
A single object: senders, campaigns, leads, invited, connected, replied — all integers, counted across the whole workspace.
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.
{
"senders": 4,
"campaigns": 3,
"leads": 1240,
"invited": 612,
"connected": 203,
"replied": 47
}Worth knowing
invited counts enrollments that have left the queued state; connected counts states connected, messaged, replied and done. A lead that replies is therefore counted in all three.
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.