Skip to main content
Glama

move_message

Destructive

Moves selected email messages to a target mailbox using message IDs, with confirmation required for bulk moves to Trash or Junk.

Instructions

Move messages (at most 100) to a mailbox. Each moved message gets a new id. A move of more than 10 messages to Trash or Junk needs 'confirm' true. If Mail is not running, applesauce opens it hidden in the background and leaves it open.

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": "move_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage ids from search_mail. At most 100.
accountNoAccount name or id of the target mailbox. Default: the account of each message.
confirmNoMust be true for a large or final delete. Without it, nothing changes and the result says why.
mailboxYesName or path of the target mailbox.
in_accountNoAccount id of the message (the 'account_id' field of search_mail). Only needed with 'in_mailbox'.
in_mailboxNoMailbox path of the message (the 'mailbox' field of search_mail). Only needed when Full Disk Access is missing. Give 'in_account' too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, yet the description still adds value: moved messages receive new ids, the confirm gate blocks changes until satisfied, and the tool will launch Mail hidden in the background and leave it open. It does not address reversibility/undo or whether a Trash move is recoverable, which keeps it short of a 5 for a destructive operation.

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?

Three short sentences, front-loaded with the action and cap, then the confirm condition, then the side effect — each sentence carries a distinct fact. The stray token "applesauce" in the third sentence is a likely redaction artifact that adds mild noise to an otherwise tight definition.

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?

For a destructive, six-parameter mutation with no output schema, the description covers the batch limit, the id-change consequence, the confirm precondition, and the app-launch side effect. The main remaining gap is the absence of any statement about failure/partial-batch behavior or undo, though the schema's confirm field hints that the result explains failures.

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 already 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it pins the confirm threshold to ">10 messages to Trash or Junk," where the schema only says "large or final delete." It also restates the 100-id cap as a hard operational constraint, reinforcing the array boundary.

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 leads with a specific verb and resource ("Move messages ... to a mailbox") plus a hard batch cap of 100, so the agent knows exactly what operation it performs. It never names a sibling such as delete_message or move_note, so the boundary with those tools must be inferred from the 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 Guidelines3/5

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

Usage context is implied rather than stated: the confirm rule for bulk moves to Trash/Junk and the note that Mail is launched if not running tell the agent when this tool needs extra care. There is no explicit when-to-use / when-not-to-use guidance or routing away from destructive siblings like delete_message or folder-move alternatives.

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