Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Trash emails

trash_emails
Destructive

Move one or more email messages to Trash for recoverable deletion; use it when users ask to delete, trash, or bin mail rather than archive it.

Instructions

Move one or more messages to the Trash. Use this only when the user asks to delete, trash, or bin mail; to clear the inbox without deleting, use archive_emails, and to file into a folder use move_emails. Trashed messages stay recoverable in the mail client until Trash is emptied; there is no permanent delete of mail. Re-running it on the same ids is harmless. Takes message ids from search_emails, get_thread or list_drafts. This also trashes a staged draft (pass the messageId list_drafts shows for it); get_draft, update_draft and send_draft then refuse it, and it stays restorable. Only when the user wants a draft gone for good, use delete_draft. Reports how many messages were trashed and lists any id the server refused.

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": "trash_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage ids to act on (1–50), as returned by search_emails or get_thread. To act on a whole conversation, pass every id get_thread lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: messages remain recoverable until Trash is emptied, there is no permanent mail delete, and trashing a staged draft causes get_draft/update_draft/send_draft to refuse it. One tension: "Re-running it on the same ids is harmless" reads as idempotent while annotations declare idempotentHint=false, so the agent gets slightly mixed signals about repeat invocations.

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-loads the action, then alternatives, then side effects and return behavior — a sensible order with almost no filler. It is on the long side (five sentences including a parenthetical draft explanation), but each sentence carries distinct information.

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

Completeness5/5

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

No output schema exists, and the description compensates by stating that it reports a count of trashed messages and lists refused ids. Combined with the recoverability semantics and draft side effects, an agent has everything needed to call and interpret this 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% and the schema already documents the 1-50 id list and the whole-conversation tip, so the description only echoes that ids come from search_emails/get_thread/list_drafts. It adds marginal routing value but no new syntax or format meaning 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?

Opens with a specific verb and resource ("Move one or more messages to the Trash") and immediately distinguishes itself from archive_emails, move_emails and delete_draft by name. An agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ("only when the user asks to delete, trash, or bin mail") plus two named alternatives with their selecting conditions (clear inbox -> archive_emails, file into folder -> move_emails). Also carves out the draft case: permanent draft removal goes to delete_draft.

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