Skip to main content
Glama

delete_message

Destructive

Delete up to 100 email messages by ID, moving them to Trash; require confirmation for bulk deletes or final removal of messages already in Trash.

Instructions

Delete messages (at most 100). Mail moves them to the Trash mailbox. Each deleted message gets a new id. More than 10 messages, or any message already in the Trash (that delete is final), needs 'confirm' true. If Mail is not running, applesauce opens it hidden in the background and leaves it open.

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": {
      "ids": "<ids>"
    },
    "name": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage ids from search_mail. At most 100.
confirmNoMust be true for a large or final delete. Without it, nothing changes and the result says why.
in_accountNoAccount id of the message (the 'account_id' field of search_mail). Only needed with 'in_mailbox'.
in_mailboxNoMailbox path of the message (the 'mailbox' field of search_mail). Only needed when Full Disk Access is missing. Give 'in_account' too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already mark this as destructive and non-read-only, and the description adds substantial context beyond them: messages move to Trash, each gets a new id, deletions over 10 or of Trash-resident messages are final and require confirm true, and Mail may be opened hidden in the background.

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?

The description is front-loaded with the core action and then adds only behaviorally relevant details. Each sentence carries useful information about scope, side effects, confirmation, or environment behavior.

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

Completeness4/5

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

For a destructive tool with annotations and a fully described input schema, the description covers the important behavioral facts: Trash placement, new ids, confirm thresholds, and app launching. There is no output schema, and the description does not explain the success response or partial-failure behavior in detail, leaving a minor gap.

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 the schema already documents all four parameters. The description still adds useful meaning by specifying the "more than 10" threshold for confirm and reinforcing the 100-message limit on ids, though it does not elaborate on in_account or in_mailbox beyond the 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?

The description states a specific verb and resource with scope: "Delete messages (at most 100)." It also explains Trash behavior and new ids, making clear that this is message deletion rather than a sibling operation like move_message or delete_calendar.

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

Usage Guidelines4/5

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

It gives clear conditions for the confirm gate: more than 10 messages, or deleting any message already in Trash, which is final. It does not name a non-destructive alternative such as move_message, so the when-to-use guidance is strong but not fully comparative.

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