Skip to main content
Glama
chandshy
by chandshy

Bulk Move Emails

bulk_move_emails

Move multiple emails to a target folder in a single API call, with progress notifications and success/failure counts.

Instructions

Move multiple emails to a folder in one call. 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
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?

Description adds beyond annotations: 'Emits progress notifications if a progressToken is provided in _meta', 'Returns success/failed counts', and warns about silent no-op on missing sourceFolder. Annotation contradiction is false.

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 sentences, each concise and informative: purpose, behavioral detail, parameter guidance. No filler words.

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 4 parameters, output schema exists, and complexity of IMAP details, the description covers purpose, behavior, parameter nuances, and return values adequately.

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%, so baseline is 3. Description adds significant value for 'sourceFolder' parameter: explains folder-scoped UIDs, warns against using 'All Mail', which is crucial context beyond schema.

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?

Description uses specific verb 'Move multiple emails to a folder in one call', clearly distinguishing from siblings like 'move_email' (single) and 'bulk_move_to_label' (different action).

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?

Explicit guidance: 'Pass sourceFolder whenever the UIDs came from a folder other than INBOX' and 'Avoid passing All Mail as the source', with reasoning about IMAP UIDs and silent no-op. Clearly states when and when not to use parameters.

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