Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

batch-delete-messages

Remove up to 100 email messages at once by moving them to Trash. Get clear counts of deleted and failed messages plus failure reasons to verify the cleanup.

Instructions

Use when: deleting multiple messages in one call (1–100 ids; moves them to Trash). Returns: counts of how many were deleted and how many failed, plus the distinct reasons for any failures. Do not use when: deleting just one (use delete-message) or filing messages away (use batch-move-messages). Safety: destructive and applies to many messages at once — require explicit user confirmation, and search-messages/list-messages first to confirm every id is correct before deleting. Pass sourceMailbox/sourceAccount (the mailbox you listed the ids from) so each numeric id is pinned to that mailbox; an id that matches in several mailboxes is refused, not guessed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
sourceAccountNoAccount the numeric ids were listed from. Required when sourceMailbox is supplied; on its own it pins nothing.
sourceMailboxNoMailbox the numeric ids were listed from (e.g. 'INBOX'). Must be paired with sourceAccount to form an unambiguous scope. Ignored for imap: ids.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
errorsNo
failedNo
mailboxNo
successNo
countDeltaNo
errorsTruncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.16.1
    • changedOutput schema / properties / countDelta / items / properties / status / enum
      Previous value: -[
-  "match",
-  "over",
-  "under",
-  "unknown"
-]New value: +[
+  "match",
+  "over",
+  "unknown"
+]
    • addedOutput schema / properties / countDelta / items / properties / unknownReason
      Added value: +{
+  "enum": [
+    "count-unreadable",
+    "no-expectation",
+    "count-did-not-move",
+    "count-partial"
+  ],
+  "type": "string"
+}
  2. Changed7 schema fields changedv2.10.24
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / sourceAccount
      Added value: +{
+  "description": "Account the numeric ids were listed from. Required when sourceMailbox is supplied; on its own it pins nothing.",
+  "type": "string"
+}
    • addedInput schema / properties / sourceMailbox
      Added value: +{
+  "description": "Mailbox the numeric ids were listed from (e.g. 'INBOX'). Must be paired with sourceAccount to form an unambiguous scope. Ignored for imap: ids.",
+  "type": "string"
+}
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / properties / countDelta
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account": {
+        "type": "string"
+      },
+      "after": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "before": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "expected": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "mailbox": {
+        "type": "string"
+      },
+      "note": {
+        "type": "string"
+      },
+      "observed": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "status": {
+        "enum": [
+          "match",
+          "over",
+          "under",
+          "unknown"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / errors
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / errorsTruncated
      Added value: +{
+  "type": "boolean"
+}
  3. Changed1 schema field changedv2.10.8
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  4. Addedv2.8.14
  5. Removedv2.8.10
  6. First observedv2.6.1

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the transparency burden. It discloses that messages are moved to Trash, returns counts and failure reasons, warns it is destructive, requires explicit user confirmation, and explains the subtle id-scoping rule (ambiguous ids are 'refused, not guessed'). No contradiction with annotations since none exist.

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?

The description is organized into clear labeled sections ('Use when', 'Do not use when', 'Safety'), each sentence earning its place. It is slightly longer than necessary—some redundancy between 'moves them to Trash' and 'destructive'—but every detail serves a purpose, making it highly scannable and dense.

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?

Given the moderate complexity from the bulk operation, scoping rules, and failure modes, the description covers all essentials: what it does, what it returns, when not to use it, and critical safety/precondition steps. It does not explicitly state idempotency or concurrency behavior, but nothing important is missing for this tool's usage.

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

Parameters4/5

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

Schema coverage is 67% (sourceAccount and sourceMailbox have descriptions, ids does not). The description adds substantial meaning to the 'ids' parameter (1–100, mailbox-scoped) and explains how sourceMailbox/sourceAccount pin ids to a mailbox and how ambiguous matches are handled, going well beyond the schema's basic field descriptions.

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 clearly states the tool's purpose: 'deleting multiple messages in one call (1–100 ids; moves them to Trash).' It uses a specific verb-resource pairing and explicitly distinguishes itself from siblings by naming 'delete-message' (single) and 'batch-move-messages' (filing), making the purpose unambiguous.

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

Usage Guidelines5/5

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

It gives explicit 'Use when' and 'Do not use when' guidance, naming specific alternative tools (delete-message, batch-move-messages) and instructing to 'search-messages/list-messages first to confirm every id is correct before deleting.' This is model guidance for an agent.

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