Skip to main content
Glama

maily_trash

Moves a message to trash: reversible for Gmail; for IMAP it goes to server's trash folder and Maily cannot restore it. Refuses if no trash folder exists and requires user confirmation before calling.

Instructions

Moves a message to the trash. Reversible for a Gmail profile; for an IMAP profile the message goes to the server's trash folder and Maily cannot restore it. If the IMAP account has no trash folder, the tool refuses (code "no_trash_folder") and leaves the message untouched. Management action: confirm with the user before calling this tool.

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": {
      "message_id": "<message_id>"
    },
    "name": "maily_trash"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it discloses reversibility for Gmail, permanent removal implications for IMAP, the "no_trash_folder" refusal code, and that the message remains untouched on refusal. It also requires user confirmation, which is important for a destructive action.

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 action, then presents the key caveats and confirmation requirement in a tight, efficient sequence. Every sentence adds useful information without redundancy.

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 one-parameter mutation tool with no annotations or output schema, the description is largely complete: it covers side effects, failure behavior, and the confirmation requirement. The remaining gap is the unexplained message_id parameter, which an agent needs in order to call the tool correctly.

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 description coverage is 0% and the description does not explain the single required integer parameter, message_id. It does not say whether this is a Maily-internal ID, a provider ID, or how to obtain it, so the description adds essentially no parameter meaning beyond the bare 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: "Moves a message to the trash." It is immediately distinguishable from sibling tools such as maily_get_message, maily_search, and maily_send, with no ambiguity about the action.

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 operational guidance: confirm with the user before calling, and notes profile-specific behavior for Gmail vs IMAP. It does not explicitly name alternatives, but no sibling tool performs the same trash action, so the missing comparison is minor.

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