What it does
When a person asks the agent to stop, the agent can make it permanent for every account of the workspace.
Arguments
| Name | Type | Required | Meaning |
|---|---|---|---|
| kind | string | yes | person or company |
| value | string | yes | Profile URL / slug / provider id, or the company name |
| note | string | no | Why — shown whenever it stops something, e.g. "existing customer" |
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": {
"kind": {
"type": "string",
"description": "person or company"
},
"value": {
"type": "string",
"description": "Profile URL / slug / provider id, or the company name"
},
"note": {
"type": "string",
"description": "Why — shown whenever it stops something, e.g. \"existing customer\""
}
},
"required": [
"kind",
"value"
]
}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": "add_do_not_contact",
"arguments": { "kind": "person", "value": "https://www.linkedin.com/in/example", "note": "Asked not to be contacted" }
}
}'Returns
{ added: true, entry: { id, kind, value, note } }
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.
{ "added": true, "entry": { "id": "dnc_lx3…", "kind": "person", "value": "example", "note": "Asked not to be contacted" } }Worth knowing
This tool can only restrict. Removing an entry is done by a person in the console.
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 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.