Skip to main content
Glama
owlpost

owlpost

delete_email

Destructive

Moves a specified email message from its current folder to the account's Trash folder, allowing recovery from the mail client instead of permanent deletion.

Instructions

Delete a message by moving it to the account's Trash folder.

The Trash folder is discovered via SPECIAL-USE (e.g. "Deleted Messages" on iCloud, "[Gmail]/Trash" on Gmail). The message is not permanently expunged from Trash, so it can still be recovered from the mail client.

Args: account: Account name from list_accounts. folder: Folder the message is currently in. uid: Message UID in that folder.

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": {
      "account": "<account>",
      "folder": "<folder>",
      "uid": "<uid>"
    },
    "name": "delete_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
folderYes
accountYes

Output Schema

NameRequiredDescriptionDefault
toYes
uidYes
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "from": {
      +      "title": "From",
      +      "type": "string"
      +    },
      +    "to": {
      +      "title": "To",
      +      "type": "string"
      +    },
      +    "uid": {
      +      "title": "Uid",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "uid",
      +    "from",
      +    "to"
      +  ],
      +  "title": "MoveResult",
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely non-obvious behavior: the destination is resolved via SPECIAL-USE (with concrete per-provider examples) and the message is not permanently expunged, so it remains recoverable from a mail client. This is meaningful context beyond the annotations, though it says nothing about failure modes (missing UID, folder not found) or behavior when the message is already in Trash.

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?

Front-loaded with the core action and its mechanism in the first sentence, with supporting detail after. The SPECIAL-USE parenthetical earns its place by explaining how the Trash folder is located, though the provider examples are slightly longer than strictly necessary.

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 3-parameter mutation with an output schema present, the definition covers what the action does, where the data goes, and the meaning of every parameter. Missing only edge-case behavior for invalid UID or already-trashed messages, which is a modest gap rather than a blocking one.

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 description coverage is 0%, so the description must carry the parameters, and its Args block does: account is tied to list_accounts, folder is defined as the message's current folder, and uid is the message UID within that folder. The docstring-dump args are spelled out even though the formal schema gives only titles, which is real compensation; a minor gap is that it doesn't state the expected UID format despite typing it as a string.

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?

States a specific verb and resource ("Delete a message") and immediately defines the mechanism: it moves the message to the account's Trash folder rather than expunging it. That mechanism statement is what separates it from move_email in the sibling list, so an agent understands the distinction without opening a schema.

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?

Usage is implied by the mechanism (soft delete, recoverable), but there is no explicit when-to-use vs. when-not, and no named alternative — notably it never says to prefer move_email for relocating a message somewhere other than Trash. An agent must infer that from the folder semantics.

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