Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_delete

Delete a specified email by moving it to trash, or permanently remove it from an account when requested.

Instructions

Delete an email (moves to trash by default, or permanently 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>",
      "emailId": "<emailId>"
    },
    "name": "email_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdYes
accountIdYes
permanentNo
sourceFolderNoSource folder (required for IMAP/iCloud when email is not in INBOX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does add real value by disclosing that deletion defaults to trash and only becomes permanent on request, but it omits that permanent deletion is irreversible and says nothing about permission or account prerequisites.

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?

A single tight sentence with the destructive default front-loaded in the parenthetical. Nothing is wasted, though a brief irreversibility note would earn its space.

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 mutation tool with no annotations, no output schema, and sparse parameter coverage. The description should warn that permanent deletion cannot be undone and explain the sourceFolder dependency for IMAP/iCloud; neither appears.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, so the description must compensate, and it does not. The parenthetical implies the effect of the 'permanent' flag, but accountId, emailId, and the IMAP/iCloud sourceFolder requirement are never mentioned or connected to behavior.

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 ('Delete an email') and clarifies the two deletion modes. It implies single-email scope, which distinguishes it from email_batch_delete in the sibling list, but never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to pick this over email_batch_delete, no prerequisites, and no note on when the permanent mode is appropriate. Usage is only implied by the singular 'an email'.

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