Skip to main content
Glama

imap_delete_mailbox

DestructiveIdempotent

Delete a specified mailbox or folder from a chosen email account after explicit confirmation, enabling removal of unwanted folders.

Instructions

Delete a mailbox/folder

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_name": "<mailbox_name>",
      "confirm": "<confirm>"
    },
    "name": "imap_delete_mailbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesExplicit confirmation required (must be `true`)
account_idNoAccount identifier (defaults to `"default"`)default
mailbox_nameYesName of the mailbox to delete

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known without the description. The description adds nothing beyond that: it does not say whether the deletion is permanent, whether messages inside the folder are also removed, or whether the mailbox must be empty first.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but it is arguably under-specified rather than well-sized for a destructive operation. Minimum-viable terseness lands at 3.

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

Completeness2/5

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

An output schema exists and annotations cover the destructive/idempotent profile, which offsets some burden. Still, for an irreversible folder deletion the description omits whether contained messages are destroyed and what happens if the folder is missing, leaving meaningful gaps.

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%, with 'mailbox_name', 'account_id', and 'confirm' all documented in the schema, so the baseline is 3. The description contributes no additional parameter meaning such as format constraints on mailbox names or path semantics.

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 states a specific verb and resource ('Delete a mailbox/folder'), and the 'mailbox/folder' phrasing distinguishes it from the message-level siblings such as imap_delete_message and imap_bulk_delete. It does not explicitly name or contrast with any sibling, but the resource scope is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus imap_delete_message, imap_bulk_delete, or imap_rename_mailbox, and no stated preconditions. The only hint about caution comes from the schema's required 'confirm' flag, not from the description.

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