Fluxmail

Move emails

move_emails

DestructiveIdempotent

Moves up to 100 email messages to a specified destination folder other than archive or trash. Use it to file or reorganize mail across connected accounts.

Instructions

Move messages to a folder other than the archive or trash.

Input Schema

Name	Required	Description
`folder`	Yes	Destination folder name or role
`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.

Changed5 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"
+  }
+]

addedInput schema / properties / folder / maxLength
```
Added value: +512
```

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.8/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile of this mutation is covered. The description adds only the archive/trash exclusion and says nothing about failure modes (missing folder), whether existing messages are duplicated, or partial-batch behavior. With annotations carrying the main burden, a 3 fits.

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 with zero filler; the exclusion constraint is packed into the same clause as the action, and nothing is buried or repeated.

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?

An output schema exists and the annotations plus schema fully cover safety, parameters, and return values, so the short description is largely sufficient. The remaining gap is destination-folder semantics (must it pre-exist, can it be a role/name) which the folder parameter description only lightly hints at.

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% with only 3 parameters, and the schema documents folder, messageIds (max 100), and accountId fallback behavior. The description adds no parameter-level detail beyond restating 'move messages to a folder', so the baseline 3 is appropriate.

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 (Move) and resource (messages) with a destination, and the clause 'other than the archive or trash' carves out the domain covered by siblings archive_emails and trash_emails. It stops short of naming those siblings explicitly, so an agent must infer which tool to use for those two cases.

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?

Provides a genuine when-not constraint ('not archive or trash'), which is more than most definitions offer. However it never names the alternative tools (archive_emails, trash_emails) nor states prerequisites such as whether the destination folder must already exist.

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