Skip to main content
Glama

imap_move_message

Moves an email message to a specified destination mailbox within the same account using its stable message identifier.

Instructions

Move a message to mailbox

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_mailbox": "<destination_mailbox>"
    },
    "name": "imap_move_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoAccount identifier (defaults to `"default"`)default
message_idYesStable message identifier
destination_mailboxYesDestination mailbox name

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the agent knows this is a non-idempotent write that does not destroy data. The description adds nothing beyond that: no indication that the source copy is removed, no permission requirements, and no note about the same-account restriction that only appears in the schema.

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?

The single clause is front-loaded and waste-free, but at six words it is under-specified rather than genuinely concise. There is room for one short clarifying sentence without bloat.

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?

The tool is simple and the output schema plus annotations cover the return shape and safety profile, which lowers the burden. Still, important operational facts — that moves are same-account only, and how this differs from copy — are left entirely to the schema, so the description alone is not sufficient to invoke confidently.

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

Parameters3/5

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

Schema description coverage is 100%, so account_id, message_id and destination_mailbox are already documented, which sets the baseline at 3. The description does not add meaning such as whether destination_mailbox must exist or accept nested paths like "Archive/2024".

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Move a message to mailbox" gives a specific verb and resource, so the basic action is unambiguous. But it offers no differentiation from closely named siblings such as imap_copy_message or imap_bulk_move, leaving the agent to infer the move-vs-copy distinction and the single-vs-multiple scope.

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 when-to-use or when-not-to-use guidance anywhere in the description. Nothing tells the agent to prefer this over imap_copy_message when the original should be removed from the source folder, or to use imap_bulk_move for multiple messages.

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