Skip to main content
Glama

imap_bulk_move

Move up to 500 messages from one mailbox to another in a single operation. Specify message IDs and a destination mailbox.

Instructions

Move up to 500 messages to a mailbox in one operation

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

Input Schema

NameRequiredDescriptionDefault
account_idNoAccount identifier (defaults to `"default"`)default
message_idsYesList of stable message identifiers (all must be from the same mailbox)
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

A3.6/5.0
Behavior3/5

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

Annotations already declare it as a non-read-only, non-idempotent, open-world write, so the safety profile is carried by structured data. The description adds two real behavioral facts beyond that: the 500-message cap and the single-operation batch scope. It says nothing about partial-failure behavior, atomicity, or whether moved messages retain flags, which matters for a bulk mutation.

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?

A single sentence with no filler, front-loading the action and its key constraint. Nothing in it is redundant or padded.

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 100% schema coverage, full annotations, and an output schema, the description's burden is modest and the batch limit plus one-operation framing covers the essentials. The only shortfall is bulk-mutation risk detail (partial success, ordering), which is a moderate rather than severe gap at this level of structured support.

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% and all three parameters are documented, including the same-mailbox constraint on message_ids, so the description adds little. The '500' limit is a genuine value-add not present in the schema, but destination and account_id semantics are left entirely to 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?

The description gives a specific verb ('Move') and resource ('messages to a mailbox') plus a batch ceiling ('up to 500 messages ... in one operation'), which implicitly separates it from the single-message sibling imap_move_message. It never names a sibling explicitly, so the 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?

Usage is only implied by the batch framing; there is no explicit 'use this instead of imap_move_message / imap_search_and_move when ...' statement, and no prerequisite or exclusion is given. An agent can guess the intent, but must infer the routing decision entirely.

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