Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Delete draft

delete_draft
Destructive

Permanently delete an unsent draft by draftId to remove unwanted or duplicate drafts from the Drafts folder; deletion is irreversible, so use update instead to edit.

Instructions

Permanently delete an unsent draft. Use this to retire a draft that is no longer wanted — for example the earlier version after you staged a replacement with create_draft — so the user does not find duplicates in their Drafts folder. Takes the draftId create_draft or update_draft returned, or one list_drafts shows. The draft does not go to Trash and cannot be recovered; to change a draft rather than remove it, use update_draft. Sent or received mail is refused (use trash_emails for that), as is a draft whose send is in progress. Returns the deleted draft's subject and recipients.

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": {
      "draftId": "<draftId>"
    },
    "name": "delete_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYesThe draft id, as returned by create_draft, update_draft or list_drafts — edits do not change it — or a message id from search_emails with `mailbox: "Drafts"`, which an edit replaces with the draftId it returns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and idempotentHint=false, and the description adds real substance on top: the draft bypasses Trash, is unrecoverable, and the call is refused for already-sent mail or a draft mid-send. It also discloses the return payload shape without an output schema. The bar is higher given the annotations carry the safety profile, but the added irreversibility and refusal details are meaningful.

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?

Four sentences, no filler, and the permanence warning plus the primary alternative are front-loaded ahead of the provenance and return details. Density is high; a small trim of the repeated id-provenance chain would make it tighter.

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?

A single-parameter destructive operation with no output schema, yet the description still covers irreversibility, refusal conditions, alternatives, and what the call returns (subject and recipients). An agent has everything it needs to invoke this correctly and safely.

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

Parameters4/5

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

Schema description coverage is 100%, so draftId is already fully documented including the search_emails mailbox:Drafts path. The description largely restates that provenance (create_draft/update_draft/list_drafts) rather than adding new constraints, so it clears the baseline without extending much beyond the schema.

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, 'Permanently delete an unsent draft', with the permanence qualifier front-loaded. It also implicitly delineates itself from trash_emails and update_draft, so an agent can distinguish it from siblings without opening any schema.

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?

Gives an explicit when-to-use scenario (retiring a superseded draft after create_draft to avoid duplicates in the Drafts folder) and names the direct alternatives: update_draft for changing rather than removing, and trash_emails for sent or received mail. Two refusal cases (sent/received mail, in-progress send) are stated outright.

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