Delete a contact
delete_contactPermanently removes a contact's name, properties, and consent data to honor deletion requests, keeping only the address hidden for 60 days so sent unsubscribe links still work.
Instructions
Purpose: delete one contact. Its name, properties and the IP and wording recorded with its consent go at once; the address alone is kept, hidden, for 60 days so an unsubscribe link already sent still works, then removed. This is how a deletion request is honoured. NOT for: letting mail through again. An address that asked not to be contacted stays suppressed after its contact record is gone, which is the point. Returns: the id and confirmation it is gone.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"contact_id": "<contact_id>"
},
"name": "delete_contact"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| contact_id | Yes | The contact id from list_contacts. | |
| idempotency_key | No | Your own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Identifier. | |
| error | No | Present instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds. | |
| deleted | No |