mailpouch

Overview Schema Source Related Servers Discussions Admin

Move Email to Trash

move_to_trash

Destructive

Move an email to the Trash folder after confirming the destructive action. Note that labels are not preserved when the email is moved.

Instructions

Move an email to the Trash folder. Convenience wrapper for move_email targeting Trash. Note: labels are lost when an email is moved — label copies in Labels/ folders are not preserved. Destructive: requires { confirmed: true }.

Input Schema

TableJSON Schema

Name	Required	Description
`emailId`	Yes
`confirmed`	No	Must be true to execute. See requireDestructiveConfirm.
`account_id`	No	Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).
`sourceFolder`	No	Folder the UID(s) live in (e.g. INBOX, Folders/Work, Labels/Foo). Strongly recommended whenever the UIDs came from a folder other than INBOX — IMAP UIDs are folder-scoped, so without this the wrong folder may be selected and the operation may silently no-op. Avoid passing 'All Mail' as the source: it is a union view of every folder, not a real location, so moves out of it can silently do nothing — pass the message's actual folder instead. Moving to the folder a message is already in is a no-op.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`reason`	No
`success`	Yes
`messageId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.1.0Jul 5, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).",
+  "type": "string"
+}

First observedv3.0.77Jun 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description discloses critical behavioral details beyond the annotations: labels are lost when moving (label copies not preserved) and the tool requires explicit confirmation. Since annotations already mark it as destructive, this additional context about label behavior and the confirmation requirement provides valuable transparency for the agent.

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 extremely concise, consisting of only three sentences that are front-loaded with the core purpose. Every sentence adds value: the first states the function, the second explains it is a wrapper, and the third provides essential behavioral notes. No redundant or extraneous text.

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?

Given the tool's simplicity and the presence of an output schema and annotations, the description covers the key aspects: purpose, label loss behavior, and confirmation requirement. It is sufficient for correct invocation, though it could be slightly enhanced by noting that trashing is reversible (e.g., can be undone from Trash).

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?

The schema description coverage is 75%, so the schema already documents most parameters. The description adds only a reference to the confirmed parameter (mentioning the requirement), but does not elaborate on emailId, account_id, or sourceFolder beyond what the schema provides. This meets the baseline but does not add significant extra meaning.

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 clearly states 'Move an email to the Trash folder' and identifies itself as a 'Convenience wrapper for move_email targeting Trash', which clearly specifies the verb and resource while distinguishing it from the general move_email tool. This is highly specific and leaves no ambiguity about the tool's purpose.

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?

The description implies that this tool should be used when moving an email to Trash (as opposed to other destinations) and notes the requirement for confirmation ('requires { confirmed: true }'). However, it does not explicitly mention when not to use it or compare it to alternatives like delete_email or archive_email, which would provide stronger guidance.

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

Deploy Server