Skip to main content
Glama
gmail-mcp
by gchallen

delete_draft

Destructive

Permanently discards a Gmail draft by its draft ID without affecting the thread it belongs to. Use it to remove unwanted drafts and keep your mailbox clean.

Instructions

Discard a draft permanently by draft ID. Does not affect the thread it belongs to.

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
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A4/5.0
Behavior4/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 partly given. The description earns credit for adding two facts annotations cannot convey: the deletion is permanent, and the containing thread is unaffected. It omits what happens when the draft ID does not exist or whether the operation can be undone through another call.

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, front-loaded with the action and ending with the side-effect clarification. Every clause carries information; nothing is redundant.

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 one-parameter destructive operation with annotations covering the safety flags and no output schema, the description covers what is deleted, that it is permanent, and what is not affected. Only the invalid/unknown-ID failure mode is left unaddressed, which is a minor gap at this complexity.

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 0% for the single draftId parameter, so the schema contributes only a bare string type. The description's phrase "by draft ID" confirms the parameter is the draft identifier but supplies no format, source (e.g., from list_drafts or get_draft), or error semantics.

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 gives a specific verb and resource ("Discard a draft") plus the keying parameter ("by draft ID"), and it explicitly distinguishes the effect from thread-level siblings by stating the parent thread is untouched. An agent can tell this apart from trash_thread or send_draft without opening the schema.

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?

Usage is implied by the verb — discard a draft you no longer want — but the description names no alternatives and states no when-not conditions (e.g., versus trashing a message or updating the draft instead). The reader must infer that this is the irreversible-delete path.

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