Apple Mail

by yu2001-s

Overview Schema Source Related Servers Discussions Admin

batch-move-messages

Move up to 100 email messages to a specified mailbox in a single operation. Ideal for bulk organizing or archiving.

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. 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.

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": {
      "ids": "<ids>",
      "mailbox": "<mailbox>"
    },
    "name": "batch-move-messages"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes
`account`	No	Account containing the destination mailbox
`mailbox`	Yes

Output Schema

Name	Required	Description	Default
`ok`	No
`failed`	No
`mailbox`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description fully discloses that it moves many real messages, warns to confirm destination and ids, and explains return values (counts of moved and failed). Clearly a mutation operation.

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?

Four sentences, each with a distinct role: use case, returns, exclusions, safety. Front-loaded with main purpose. No unnecessary words.

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?

Includes references to sibling tools and prerequisites, return value description, and safety note. Adequate for a batch move operation with output schema.

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?

The description clarifies that ids are message identifiers (1-100) and mailbox is destination folder, adding value to the schema. However, it does not mention the optional account parameter, which has a description in schema but could be reinforced.

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 it moves multiple messages (1-100 ids) into the same destination mailbox, with an example of bulk archiving. It distinguishes from sibling tools like move-message (single) and batch-delete-messages (deleting).

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?

Explicit 'Use when' and 'Do not use when' sections, referencing specific alternatives (move-message, batch-delete-messages) and prerequisite (list-mailboxes).

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

Deploy Server