Skip to main content
Glama

Move Email Messages in Bulk

batch_move_messages
Destructive

Move multiple messages to the same folder in one call, resolving the destination once and returning a single summary with any failures reported individually.

Instructions

Move several messages to the same folder in one call. Resolves the destination once and returns a single summary instead of one result per message. Reports any failures individually.

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_ids": "<message_ids>",
      "destination": "<destination>"
    },
    "name": "batch_move_messages"
  }
}

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.
destinationYesDestination folder: well-known name (e.g. archive), display name, or folder ID
message_idsYesMessage IDs or scan_messages refs to move (max 50)

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 readOnlyHint=false and destructiveHint=true, so safety is covered structurally. The description adds genuine behavioral detail beyond that: the destination is resolved once, a single summary is returned rather than per-message results, and failures are reported individually, which tells the agent how to interpret partial success. It stops short of stating that messages are removed from the source folder or whether the move is reversible, which matters given destructiveHint=true.

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?

Three short sentences, front-loaded with the operation and scope, then the batching benefit, then the failure semantics. Every sentence carries distinct information with no filler.

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?

With three parameters, no output schema, and annotations covering the safety profile, the description covers what an agent needs: batch semantics, the shared-destination constraint, and the summary-plus-per-failure return shape. Missing only a note on source-folder removal or reversibility, which would round out a destructive operation.

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 the mailbox, destination, and message_ids parameters (including the 50-item cap and scan_messages refs) are already fully documented. The description adds only the constraint that all messages go to one shared destination, which is minor incremental meaning over the schema.

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 and resource with scope: 'Move several messages to the same folder in one call.' The 'several messages' / 'same folder' qualifiers distinguish it from a single-message move and from criteria-based moving, but no sibling is named explicitly, so differentiation is inferential rather than stated.

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?

The phrase 'in one call' implies this is the batch choice when all targets share a destination, which is useful implied guidance. However, there is no explicit when-to-use clause and no named alternative (e.g. move_message for a single item, move_messages_matching for criteria-based moves), so an agent must infer routing from the description's shape alone.

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