Skip to main content
Glama

imap_bulk_delete

DestructiveIdempotent

Delete up to 500 IMAP messages from one mailbox in a single confirmed bulk operation. Provide message IDs and explicit confirmation to remove multiple emails at once.

Instructions

Delete up to 500 messages in one operation

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_ids": "<message_ids>",
      "confirm": "<confirm>"
    },
    "name": "imap_bulk_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesExplicit confirmation required (must be `true`)
account_idNoAccount identifier (defaults to `"default"`)default
message_idsYesList of stable message identifiers (all must be from the same mailbox)

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

B3.4/5.0
Behavior3/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 covered. The description's only added fact is the 500-message cap; it says nothing about permanence (trash vs expunge), partial-failure behavior when some IDs are invalid, or the practical consequence of the required confirmation flag.

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?

A single short sentence with the destructive action and the scale limit front-loaded. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be explained, and the schema fully documents the inputs. For a destructive bulk operation the remaining gap is the absence of routing guidance versus the single-delete and search-and-delete siblings.

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 coverage is 100% and every parameter carries its own description, including the same-mailbox constraint and the mandatory confirm flag. The description adds no parameter-level meaning beyond the numeric limit already implied by 'up to 500'.

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?

States a specific verb and resource ('Delete ... messages') and adds the batch ceiling ('up to 500'), which distinguishes it from a single-message delete. It does not name or contrast with siblings such as imap_delete_message or imap_search_and_delete, so an agent must infer the boundary from names alone.

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?

No guidance on when to prefer this over imap_delete_message (one message) or imap_search_and_delete (search-driven deletion), and no mention of prerequisites such as the messages living in one mailbox. Usage must be inferred entirely from the tool name and schema.

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