Tools: Do-not-contact
add_suppression
Prevent outreach to an email or domain, including when someone asks not to be contacted.
| Group | Do-not-contact |
| Scope | crm:write |
| Who can call it | Agents and people with this scope. |
| Kind | Write. Recorded in the change history with who made it. |
| Retries | Pass idempotency_key (MCP) or the Idempotency-Key header (REST); a retry with the same key within 24 hours returns the first result. |
| Widget | Text only. |
Parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
kind | email \ | domain | yes |
value | string | yes | max 320 characters |
reason | string | yes | max 1000 characters |
Call it over MCP
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "add_suppression",
"arguments": {
"kind": "email",
"value": "…",
"reason": "…",
"idempotency_key": "log-call-acme-2026-11-02"
}
}
}
Send it to https://api.tandemcrm.app/mcp (streamable HTTP). Most people never write this by hand: their agent picks the tool from its description.
Call it over REST
curl -X POST https://api.tandemcrm.app/v1/ops/add_suppression \
-H "Authorization: Bearer $TANDEM_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: log-call-acme-2026-11-02" \
-d '{"kind":"email","value":"…","reason":"…"}'
Input schema
The JSON Schema the MCP server advertises for this tool (over MCP it also accepts idempotency_key):
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"kind": {
"type": "string",
"enum": [
"email",
"domain"
]
},
"value": {
"type": "string",
"minLength": 1,
"maxLength": 320
},
"reason": {
"type": "string",
"minLength": 1,
"maxLength": 1000
}
},
"required": [
"kind",
"value",
"reason"
]
}