Skip to main content
Glama
chandshy
by chandshy

Bulk Move Emails

bulk_move_emails

Move multiple emails to a specified folder in a single operation. Supports folder selection and confirmation for Trash or Spam moves.

Instructions

Move multiple emails to a folder in one call. Moving to Trash or Spam requires { confirmed: true }. Emits progress notifications if a progressToken is provided in _meta. Returns success/failed counts. Pass sourceFolder whenever the UIDs came from a folder other than INBOX.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailIdsYesArray of email UIDs to move
confirmedNoMust be true when targetFolder is Trash or Spam.
account_idNoOptional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).
sourceFolderNoFolder the UID(s) live in (e.g. INBOX, Folders/Work, Labels/Foo). Strongly recommended whenever the UIDs came from a folder other than INBOX — IMAP UIDs are folder-scoped, so without this the wrong folder may be selected and the operation may silently no-op. Avoid passing 'All Mail' as the source: it is a union view of every folder, not a real location, so moves out of it can silently do nothing — pass the message's actual folder instead. Moving to the folder a message is already in is a no-op.
targetFolderYesDestination folder path

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorsYes
failedYes
successYes
Behavior5/5

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

Discloses progress notifications with progressToken, return format (success/failed counts), potential silent no-op without correct sourceFolder, and no-op when moving to same folder. These are important behaviors beyond the annotations (which only indicate readOnly=false, etc.).

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?

Every sentence adds unique information; no redundancy. Purpose is front-loaded. The description is compact yet covers all critical aspects.

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?

With 5 parameters, 100% schema coverage, and presence of an output schema (implied by return mention), the description sufficiently covers usage, edge cases, and behaviors. No gaps for a tool of this complexity.

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 coverage is 100%, but description adds value: explains that emailIds are UIDs, clarifies sourceFolder's role with IMAP scoping and pitfalls, and reiterates the confirmed requirement for Trash/Spam. This goes beyond the schema descriptions.

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 starts with 'Move multiple emails to a folder in one call,' clearly stating the verb (move) and resource (emails). It distinguishes from siblings like move_email (single) and bulk_move_to_label (different target type).

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?

Provides explicit conditions: requires 'confirmed: true' for Trash/Spam, and advises to pass sourceFolder when UIDs are from non-INBOX folders, warning against 'All Mail'. Does not explicitly compare to alternatives like single move, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chandshy/mailpouch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server