Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_batch_delete

Delete multiple emails at once by ID to speed up inbox cleanup across Gmail, Outlook, iCloud, or IMAP. Optionally move to trash or permanently delete up to 1,000 messages per call.

Instructions

Delete multiple emails at once. Much faster than individual deletes.

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>"
    },
    "name": "email_batch_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdsYesArray of email IDs to delete
accountIdYes
permanentNoPermanently delete instead of moving to trash
sourceFolderNoSource folder (required for IMAP/iCloud when emails are not in INBOX)

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 for a destructive mutation. It does not say whether emails go to trash or are irrecoverable by default, what happens on partial failure, whether account-level permissions are needed, or how the response reports per-item results. The only behavioral trait disclosed is speed relative to single deletes, which is secondary for a destructive operation.

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, front-loaded sentences with the action stated first and no repetition. The second sentence is a comparative performance claim rather than actionable instruction, so it is slightly expendable but not wasteful.

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?

This is a destructive batch mutation with no annotations and no output schema, so the description must supply safety context — and it does not. Missing are the trash-vs-permanent default, irreversibility warnings, partial-success semantics, and any note that sourceFolder matters for IMAP/iCloud accounts. An agent could invoke it and silently hard-delete up to 1000 emails.

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, permanent, and sourceFolder documented inline, so the schema already does most of the explanatory work. The description adds no parameter meaning at all — notably it never mentions the permanent flag, which is the single most consequential parameter for a delete tool.

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 and resource ('Delete multiple emails at once'), making the batch nature explicit and implicitly distinguishing it from the single-item email_delete sibling. It stops short of naming any sibling or clarifying scope beyond 'multiple', so it is clear but not fully differentiating.

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 deletes' implies the tool should be preferred over email_delete for bulk work, which is a real usage hint. However, there is no explicit when-not-to-use guidance, no mention of the permanent-vs-trash choice, and no note about batch size limits (the 1000-item cap lives only in the schema).

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