Skip to main content
Glama

Move Email Message

move_message
Destructive

Move an email message to another mail folder by well-known name, display name, or folder ID; use it to archive, file, or delete messages in Microsoft 365 mailboxes.

Instructions

Move a message to another mail folder. Destination accepts a well-known name (archive, deleteditems, inbox, junkemail), a top-level folder display name, or a folder ID. A well-known name always wins over a custom folder of the same name, and the confirmation says which was used. Subfolders cannot be resolved by name — pass their ID. Moving to deleteditems is recoverable; use list_mail_folders to see what exists.

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

Input Schema

NameRequiredDescriptionDefault
mailboxNoEmail address of another mailbox to act on (delegated or shared), e.g. 'someone@example.com'. Omit for your own mailbox; required when this server signs in as an application. Only addresses this server is configured to allow will be accepted.
message_idYesThe message ID, or a short ref from scan_messages, to move
destinationYesDestination folder: well-known name (e.g. archive), display name, or folder ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write nature is known; the description goes further by explaining destination-resolution precedence (well-known name wins over a same-named custom folder), the subfolder-by-ID restriction, and that deleteditems moves are recoverable. It does not cover failure modes when a destination does not resolve or what the confirmation contains beyond naming the resolution path.

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, front-loaded with purpose, then destination resolution, then the caveat about subfolders, then recoverability and the folder-listing pointer. No sentence is redundant and each carries distinct information.

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, three-parameter mutation with no output schema, the description supplies the resolution rules, a hard limitation (subfolders by ID only), recoverability, and an exploration tool. Minor gaps remain around error behavior for unresolvable destinations and what the returned confirmation actually includes.

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 description coverage is 100%, so the baseline is 3, but the description genuinely adds meaning about the destination parameter: it enumerates the accepted well-known names, defines the precedence rule between a well-known name and a same-named custom folder, and clarifies that subfolders must be passed by ID. That is real semantic value beyond 'well-known name, display name, or folder ID'.

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 opening sentence gives a specific verb and resource: 'Move a message to another mail folder.' An agent can immediately tell this is a single-message move. It stops short of naming the batch siblings (batch_move_messages, move_messages_matching), so the single-vs-bulk distinction is left implicit.

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

Usage Guidelines4/5

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

It points the agent to list_mail_folders to discover valid destinations and warns that subfolders cannot be resolved by name, which is actionable guidance for choosing correct arguments. It does not state when to prefer this tool over the batch move siblings, so it falls short of full when/when-not coverage.

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