Skip to main content
Glama

Mail Move Message

mail_move_message

Move or archive an Apple Mail message by specifying its message ID and target mailbox, letting an AI client file mail into the correct folder.

Instructions

Move/archive a message.

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_id": "<message_id>",
      "target_mailbox": "<target_mailbox>"
    },
    "name": "mail_move_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes
target_mailboxYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden for a mutation, and it discloses almost nothing: it does not say the message disappears from its source mailbox, whether the operation is reversible, what happens if target_mailbox does not exist, or what permissions are needed. The slash construction "Move/archive" also blurs whether archiving is a distinct behavior or just the common target of a move.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

There is no wasted wording and the verb is front-loaded, but the single fragment is under-specified rather than concise. Brevity here costs information rather than saving it.

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

Completeness2/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 described, but this is a mutation tool with zero annotation coverage and undocumented parameters, and the description supplies none of the missing safety or targeting context. It is not sufficient for an agent to call it correctly and confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and it does not mention either parameter. The names message_id and target_mailbox are partly self-explanatory, but whether target_mailbox expects a display name, an ID, or a full path is left entirely unresolved.

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 pair ("Move/archive") and resource ("a message"), so an agent can tell it apart from send/get/search siblings. It stops short of differentiating itself from mail_mark_message or explaining how "archive" differs from "move", so it is clear but not fully disambiguated.

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?

There is no guidance on when to use this versus mail_mark_message or other mailbox-altering siblings, and no stated preconditions. An agent must infer the use case entirely from the name and verb.

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