Fluxmail

modify_emails

Destructive

Batch-update emails by marking read/unread, starring, archiving, trashing, moving, or applying labels across connected accounts.

Instructions

Batch-modify emails using the actions allowed for this connection. Moving requires folder; labels require labels.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes
`folder`	No	Target folder for action=move
`labels`	No	Labels for addLabels/removeLabels
`accountId`	No	Account to operate on. Optional when exactly one account is connected.
`messageIds`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.1Oct 1, 2026
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```

Changed1 schema field changedv0.11.0Sep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "failed": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "messageId": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "messageId",
+              "code"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "succeededIds": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "uncertainIds": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "action",
+        "succeededIds",
+        "failed",
+        "uncertainIds"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jul 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, and the description does not contradict that. However, beyond the annotation the description adds almost nothing about destructive behavior: it does not specify which actions are irreversible, whether delete is permanent versus trash, or what permissions are needed.

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?

Two short sentences with the purpose front-loaded. The second sentence adds useful conditional parameter requirements without any wasted words.

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

Completeness2/5

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

For an 11-action destructive mutation tool, the description leaves major gaps: which actions are destructive, whether delete is permanent, and connection-dependent authorization details. The presence of an output schema means return values need not be explained, but behavioral context is still insufficient.

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?

The description restates conditional requirements already present in the schema for folder and labels. It adds no meaning for the action enum or messageIds, and with only 60% schema description coverage it does not compensate for missing parameter details.

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 ('batch-modify emails') and notes the action set is connection-dependent. It is clearly distinct from read/list/send siblings, but does not explicitly differentiate itself from them by name.

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

Usage Guidelines2/5

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

Gives only conditional parameter requirements ('Moving requires folder; labels require labels'), not guidance on when to choose this tool over alternatives or when not to use it. No alternative tools are mentioned.

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