Fluxmail

Move emails to trash

trash_emails

DestructiveIdempotent

Move selected email messages to the trash, where they stay recoverable until your provider empties it. Useful for clearing inbox clutter without permanently deleting mail.

Instructions

Move messages to the trash, where they can be restored until the provider empties it.

Input Schema

Name	Required	Description	Default
`accountId`	No	Account to operate on. Optional when exactly one account is connected.
`messageIds`	Yes	Messages to change, up to 100 IDs

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.19.0Oct 30, 2026

changedInput schema / properties / accountId / anyOf

Previous value: -[
-  {
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 512,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / messageIds / description

Previous value: -"Messages to change, up to 100 distinct IDs"New value: +"Messages to change, up to 100 IDs"

addedInput schema / properties / messageIds / items / maxLength
```
Added value: +512
```
addedInput schema / properties / messageIds / maxItems
```
Added value: +100
```

Addedv0.16.0Oct 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: trashing is recoverable until the provider empties it. It does not explain provider-dependent retention timing or permission requirements, but the core behavior is disclosed.

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?

A single sentence, front-loaded with the action and destination, with no redundant restatement of the name or title. Its size matches a simple two-parameter tool and every phrase adds value.

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?

For a two-parameter tool with full schema coverage, an output schema, and rich annotations, the description supplies the one important non-schema nuance: recoverability. Nothing essential for correct invocation is missing.

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 description coverage is 100%, so accountId and messageIds are fully documented in the schema. The description adds no parameter-level meaning beyond the schema, making 3 the appropriate baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: move messages to the trash, and clarifies that this is not permanent deletion because messages can be restored. It does not explicitly differentiate from sibling tools such as archive_emails or move_emails, so it falls short of 5.

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?

The description implies usage for recoverable removal and gives the key context that messages remain restorable until the provider empties trash. However, it does not say when to choose trash_emails over archive_emails, move_emails, or permanent deletion, and it provides no exclusions.

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