nc-mcp-server

move_mail_message

Move an email to a different mailbox in the same account. Requires message ID and destination mailbox ID; the message receives a new ID after moving.

Instructions

Move a message to another mailbox (folder) of the same mail account.

Mail cannot move messages between accounts; such a move fails with "It is not possible to move across accounts yet".

The moved message gets a new ID, so message_id is no longer valid afterwards and must not be reused. IMAP UIDs are per mailbox, and Nextcloud assigns the new ID when it syncs the destination mailbox. The inbox and mailboxes with background sync enabled are synced automatically; other folders are synced when opened in the Mail app. A message that is already in the destination mailbox is left alone and keeps its ID.

Args: message_id: The message database ID. Use list_mail_messages to find it. destination_mailbox_id: The target mailbox ID, in the message's own account. Use list_mailboxes to find it.

Returns: Confirmation message on success.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`message_id`	Yes
`destination_mailbox_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses crucial behavioral details: the moved message gets a new ID and the old message_id becomes invalid, IMAP UIDs are per-mailbox, sync behavior depends on folder settings, and moving to the same mailbox is a no-op. This goes far beyond what annotations provide.

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: main purpose first, then critical caveats, parameter explanations, and return behavior. Every sentence adds value—no filler, and important details like the cross-account failure message and ID invalidation are included without bloat.

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 the moving operation's subtle side effects (new ID, sync behavior, same-mailbox no-op), the description covers all necessary guidance. It names both parameters, explains the failure mode, and states the successful return. No additional information is needed for correct 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?

Schema coverage is 0%, so the description carries full responsibility. It explains message_id as 'The message database ID' with guidance to use list_mail_messages, and destination_mailbox_id as 'target mailbox ID, in the message's own account' with list_mailboxes guidance. This adds real semantic meaning beyond the bare integer types.

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 opens with a precise verb+resource+target: 'Move a message to another mailbox (folder) of the same mail account.' This clearly distinguishes it from sibling tools like copy_file or move_file, and no other mail-specific move tool exists among siblings.

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?

It explicitly states the same-account constraint and warns that cross-account moves fail, which tells the agent when not to use this tool. It also gives concrete instructions to find message_id via list_mail_messages and destination_mailbox_id via list_mailboxes, plus behavior for already-located messages.

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

Deploy Server