Skip to main content
Glama
Albretsen

MCP Emails

Delete Email

email_delete
Destructive

Delete emails from an inbox individually, in batches, or by search criteria. Moves messages to Trash by default; use permanent to hard-delete them.

Instructions

Delete messages in one inbox. Flagged DESTRUCTIVE so your MCP client can ask for confirmation first. Deleted mail goes to Trash and stays recoverable unless you pass permanent: true, which is irreversible. Needs the delete:email scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCc recipient to match: address, name, or fragment.
toNoTo recipient to match: address, name, or fragment.
bodyNoText to find in the body. On Gmail this matches the whole message.
fromNoSender to match: address, name, or fragment.
textNoText to match anywhere, headers included.
inboxNoInbox email address; an alternative to inbox_id, which wins when both are given.
limitNoCap on messages deleted. Default 500.
queryNoProvider-native raw query (escape hatch); prefer the structured fields. Ignored on Fastmail.
sinceNoReceived on or after this date or datetime (no timezone = UTC).
actionYesOperation to run. delete = one message_id; delete_batch = up to 500 message_ids; search_and_delete = every message matching a search.
beforeNoReceived strictly before this date or datetime (no timezone = UTC).
unreadNotrue = unread only; false = read only; omit for both.
flaggedNotrue = only flagged/starred messages. Ignored on Outlook.
subjectNoText to match in the subject; phrases match as-is.
inbox_idNoInbox UUID. Optional when the key has exactly one inbox. Otherwise pass this or `inbox`; omit both and the error lists every inbox_id.
permanentNoHard-delete, bypassing Trash. Default false, which trashes it.
message_idNoProvider-native message id from a list or search.
message_idsNoProvider-native message ids to delete.
has_attachmentNotrue = only messages with an attachment. Ignored on generic IMAP.
idempotency_keyNoOpaque key for one operation, outbound or mailbox mutation. Reuse it only when retrying the identical request within 24 hours: the retry is collapsed, not repeated, which matters most for copy. Reuse with different arguments is rejected; omit it for normal behaviour.
include_foldersNoFolder names to search.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.4

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses that mail goes to Trash and is recoverable unless permanent:true is passed, introduces the irreversible case, and calls out that the MCP client should ask for confirmation. It adds meaningful behavioral context beyond the annotations and does not contradict them.

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 concise sentences: the first front-loads the action and scope, the second addresses safety/confirmation, and the third covers recovery, irreversibility, and auth. Every sentence earns its place with zero fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a complex 21-parameter conditional schema with three action modes, the description does not mention delete, delete_batch, or search_and_delete, nor the filter-based search behavior. The schema compensates heavily, but the description alone would be incomplete for an agent deciding how to invoke this destructive multi-mode tool.

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 coverage is 100% with rich descriptions on every parameter, including action modes, filters, and permanent. The description itself adds no parameter-level meaning beyond highlighting permanent:true, which the schema already documents. 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?

The description states a clear verb and resource: 'Delete messages in one inbox.' It is unambiguous about the core purpose. However, it does not explicitly differentiate from siblings like email_organize or bulk_cancel, leaving the agent to rely on the name for disambiguation.

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?

The description implies usage for deleting messages and notes the required delete:email scope, but gives no explicit when-to-use guidance, exclusions, or alternatives among sibling tools. It also does not explain when to choose delete vs delete_batch vs search_and_delete—that is left to the schema.

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

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/Albretsen/MCPEmails'

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