Skip to main content
Glama
mail-mcp-server

mail-mcp-server

plan_delete_draft

Preview permanent deletion of a draft without changing anything; returns affected items and a plan ID so you can show a summary and get approval before executing.

Instructions

Dry run: changes nothing. Returns what would be affected and a plan_id for execute_plan. Show the user the summary before asking whether to execute. Delete a draft. Permanent: drafts do not go to Trash.

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": {
      "mailbox": "<mailbox>",
      "draft_id": "<draft_id>"
    },
    "name": "plan_delete_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxYesA connected mailbox address (see list_mailboxes)
draft_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares the call is a dry run that changes nothing, states what is returned (affected items plus plan_id), and warns that the eventual deletion is permanent because drafts bypass Trash. It omits any note on required permissions or the exact shape of the summary.

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 short sentences with no filler, and the most decision-relevant fact ("Dry run: changes nothing") is front-loaded. The core purpose statement sits in the middle rather than leading, which slightly hurts scanability but costs no extra length.

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?

There is no output schema, so the description must cover return values, and it does name the two key outputs (affected items, plan_id). For a two-parameter preview tool that is nearly sufficient; only the draft_id semantics remain unaddressed.

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

Parameters2/5

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

Schema coverage is only 50%: mailbox is documented inline (pointing at list_mailboxes) but draft_id has no description in the schema, and the tool description adds no meaning for either parameter. It neither clarifies the draft_id format nor explains how affected items relate to the mailbox argument.

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

Purpose4/5

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

The description names a specific verb and resource ("Delete a draft") and frames it as a non-mutating preview step whose output feeds execute_plan. An agent can tell this apart from the execute_plan sibling, though the naming of other plan_delete_* variants is left to inference from the resource word.

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?

It states the intended workflow explicitly: call this, show the user the summary, then ask whether to execute. That is clear when-to-use context plus a pointer to the follow-up tool. It stops short of naming when not to use it (e.g., cases where a plan is unnecessary).

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