Tools: Do-not-contact
remove_suppression
Remove a do-not-contact entry. Only a signed-in workspace admin can do this.
| Group | Do-not-contact |
| Scope | crm:delete |
| Who can call it | Signed-in people only. Agents don't see this tool over MCP, and calling it with an API key returns forbidden. People use it in the Tandem app. |
| Kind | Write. Recorded in the change history with who made it. Destructive (destructiveHint: true). |
| 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 |
|---|---|---|---|
id | id (uuid) | yes |
Call it over MCP
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "remove_suppression",
"arguments": {
"id": "00000000-0000-4000-8000-000000000000",
"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/remove_suppression \
-H "Authorization: Bearer $TANDEM_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: log-call-acme-2026-11-02" \
-d '{"id":"00000000-0000-4000-8000-000000000000"}'
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": {
"id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
}
},
"required": [
"id"
]
}