Skip to main content
Glama
agentisend

agentisend

Delete a contact

delete_contact
DestructiveIdempotent

Permanently 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

NameRequiredDescriptionDefault
contact_idYesThe contact id from list_contacts.
idempotency_keyNoYour 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

NameRequiredDescriptionDefault
idNoIdentifier.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds real substance on top: exactly what is erased (name, properties, consent IP and wording), the 60-day hidden tombstone of the address so existing unsubscribe links keep working, and that suppression survives record deletion. That is the precise information an agent needs before performing an irreversible write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The Purpose / NOT for / Returns labeling front-loads the important content and makes scanning easy. Some phrasing is heavier than needed ('the IP and wording recorded with its consent'), but no sentence is filler given the destructive nature of the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive one-parameter delete with an output schema already covering the return shape, the description supplies the remaining unknowns: what data is destroyed, what is retained and for how long, and the lasting side effect on suppression. Nothing an agent needs to call this safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters (contact_id with UUID pattern pointing at list_contacts, idempotency_key with retry semantics) are fully documented in the schema. The description adds no additional meaning about either parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('delete one contact') with explicit scope, and distinguishes it from the adjacent suppression behavior by declaring 'NOT for: letting mail through again.' An agent can tell this apart from add_suppression/remove_suppression without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear positive context ('This is how a deletion request is honoured') and an explicit exclusion ('NOT for: letting mail through again'), so the when-not is unambiguous. It does not name the sibling tool an agent should use for mail-flow questions, which keeps it from a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.