Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_batch_move

Move multiple emails to a target folder in one batch operation, reducing the need to move messages individually across Gmail, Outlook, iCloud, or IMAP accounts.

Instructions

Move multiple emails to a folder at once. Much faster than individual moves.

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": {
      "accountId": "<accountId>",
      "emailIds": "<emailIds>",
      "targetFolder": "<targetFolder>"
    },
    "name": "email_batch_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdsYesArray of email IDs to move
accountIdYes
sourceFolderNoSource folder (required for IMAP/iCloud when emails are not in INBOX)
targetFolderYesDestination folder name or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses nothing about required permissions, whether the move is reversible, what happens if a target folder does not exist, or the IMAP/iCloud sourceFolder constraint — all of which an agent needs before invoking a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, purpose front-loaded with zero filler. The second sentence is partly promotional but does convey a meaningful performance rationale for the batch variant.

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?

For a four-parameter mutating tool with no annotations and no output schema, the description is thin — it omits failure modes, the 1000-item cap, account scoping, and the sourceFolder requirement for IMAP/iCloud when not in INBOX. An agent could call it but could easily misuse it.

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 75%, with emailIds, sourceFolder, and targetFolder all documented in-schema and only accountId left bare. The description adds no syntax or folder-resolution detail beyond the schema, so the baseline 3 is appropriate.

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 — moving multiple emails to a folder — plus the 'at once' batching scope, which implicitly separates it from the single-email email_move sibling. It never names that sibling explicitly, so the differentiation is inferred 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?

'Much faster than individual moves' implies the batch tool should be preferred when handling several emails, but it gives no explicit when-to-use rule, no threshold, and no named alternative such as email_move for a single message. Usage is only implied.

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