Skip to main content
Glama

Delete Email Draft

delete_draft
Destructive

Delete an unsent draft email by message ID, optionally from a shared or delegated mailbox. Refuses non-draft messages so sent or received mail stays intact.

Instructions

Delete an unsent draft. Refuses any message that is not a draft.

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

Input Schema

NameRequiredDescriptionDefault
mailboxNoEmail address of another mailbox to act on (delegated or shared), e.g. 'someone@example.com'. Omit for your own mailbox; required when this server signs in as an application. Only addresses this server is configured to allow will be accepted.
message_idYesThe draft's message ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds genuinely new behavior — that non-draft messages are rejected — but says nothing about whether the deletion is permanent, recoverable, or how failures surface. With annotations carrying the safety bar, this is adequate but thin.

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?

Two short sentences, zero filler, with the operation stated first and the guardrail second. Nothing could be removed without losing information.

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

Completeness4/5

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

For a simple two-parameter delete with full schema coverage and annotations, the definition is close to sufficient. The remaining gap is whether a deleted draft is permanently gone or recoverable, plus any auth implications of delegated mailbox access, which the description leaves to the schema.

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 description coverage is 100%, so both message_id and the mailbox delegation parameter are fully documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 states a specific verb and resource ("Delete an unsent draft") and narrows the scope to drafts only, which separates it from sibling writers like update_draft, send_draft, and the other delete_* tools. The second sentence reinforces the resource boundary rather than restating the name.

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

Usage Guidelines3/5

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

There is a clear precondition (the message must be a draft), but no guidance on when to delete a draft versus updating it or sending it, and no mention of the batch alternatives. Usage is implied by the verb rather than taught.

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

Deploy Server

Other Tools