What it does
Know who is off limits before prospecting.
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": "list_do_not_contact",
"arguments": {}
}
}'Returns
{ count, entries: [{ id, kind, value, label, note, created_at }] }
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.
{ "count": 1, "entries": [{ "id": "dnc_lx3…", "kind": "company", "value": "acme corp", "label": null, "note": "existing customer", "created_at": "2026-10-05T09:00:00.000Z" }] }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
add_do_not_contact
Add a person or a company to the do-not-contact list. It can only stop outreach, never start it.
check_reachability
Before reaching out: degree of connection, pending invitation, whether a connection request, a message or an InMail can go to this person — and whether the do-not-contact list or another account of the workspace already covers them
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.