Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

batch-move-messages

Move up to 100 email messages to a chosen mailbox in one call, with per-batch success and failure counts plus failure reasons.

Instructions

Use when: moving multiple messages (1–100 ids) into the same destination mailbox/folder in one call, e.g. bulk archiving. Returns: counts of how many were moved and how many failed, plus the distinct reasons for any failures. Do not use when: moving just one (use move-message) or deleting (use batch-delete-messages). Use list-mailboxes to confirm the destination name exists. Safety: moves many real messages at once — confirm the destination mailbox, and search-messages/list-messages first to confirm the ids. Pass sourceMailbox/sourceAccount (the mailbox you listed the ids from — not the destination) 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
accountNoAccount containing the destination mailbox
mailboxYes
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. Dates show when Glama detected each change.

  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

A5/5.0
Behavior5/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It warns that the operation moves many real messages, explains that ambiguous ids are refused rather than guessed, describes return counts and failure reasons, and explains the sourceMailbox/sourceAccount scoping semantics.

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?

The description is well-structured with labeled sections (Use when, Returns, Do not use when, Safety) and every sentence adds useful information. It is longer than average but each part earns its place given the complexity and safety considerations.

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

Completeness5/5

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

Given there are 5 parameters, no annotations, and the high-stakes mutating nature of the operation, the description provides comprehensive context: when to use, when not to use, prerequisites, return values, safety warnings, and precise parameter semantics. It is sufficient for correct tool invocation.

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

Parameters5/5

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

The schema covers only 60% of parameters, but the description significantly compensates. It clarifies the distinction between destination mailbox and sourceMailbox, requires sourceAccount pairing, explains imap: id behavior is ignored for source scoping, and clarifies that ids must be pinned to the source mailbox.

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 operation: moving multiple messages (1–100 ids) into the same destination mailbox/folder in one call. It explicitly references the tool name's scope and distinguishes it from related tools by exclusion.

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?

Provides explicit when-to-use guidance, concrete when-not-to-use cases with alternative tool names (move-message, batch-delete-messages), and prerequisite advice to verify destination with list-mailboxes and confirm ids with search/list-messages.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sweetrb/apple-mail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server