Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Delete contact

delete_contact
Destructive

Deletes a contact by ID from the account and all syncing devices; use it to remove address-book records, noting header- or calendar-derived contacts may reappear on the next incoming message.

Instructions

Delete a contact by id, removing it from the account and from every device syncing the address book. A contact derived from mail headers or calendar attendees is only removed until the next message from that person recreates it — to drop one field instead of the whole record, use update_contact; if it duplicates another contact of the same person or organization, use merge_contacts, which keeps its addresses, notes and history. Find the id with search_contacts.

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": {
      "contactId": "<contactId>"
    },
    "name": "delete_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactIdYesThe contact id, as printed by search_contacts under `contact_id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds real value beyond that by disclosing propagation to every syncing device and the resurrection behavior for contacts derived from mail headers or calendar attendees. It stops short of stating permission requirements or whether deletion is reversible, so it is strong but not fully exhaustive.

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

Conciseness5/5

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

Three sentences, front-loaded with the action and its blast radius, then the caveat, then the disambiguation. Every clause carries information an agent needs, with no filler.

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 one-parameter destructive delete with no output schema, the definition covers effect, propagation scope, the derived-contact exception, id discovery, and both competing alternatives. An agent can call this correctly and confidently without further information.

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 the single property already documents that the id comes from search_contacts under contact_id, so the schema carries the burden. The description's 'by id' phrasing and its pointer to the same lookup tool add essentially no meaning beyond that.

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?

The description opens with a specific verb+resource ('Delete a contact by id') and immediately scopes the effect ('removing it from the account and from every device syncing the address book'). It is unmistakably distinct from update_contact and merge_contacts, which are named as the relevant alternatives.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use update_contact to drop a single field, merge_contacts when the record duplicates another person/organization, and search_contacts to obtain the id. Each alternative comes with the condition that selects it, leaving nothing to inference.

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