Fluxmail Cloud

Remove labels

remove_labels

Idempotent

Remove labels, or Outlook categories, from messages.

Input Schema

Name	Required	Description
`labels`	Yes	Gmail labels or Outlook categories
`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.

Changed1 schema field changedOct 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

Changed5 schema fields changedOct 29, 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 / labels / items / 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
```

Changed11 schema fields changedOct 27, 2026
- changedInput schema / $schema
```
Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / properties / accountId / anyOf
```
Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / accountId / description
```
Added value: +"Account to operate on. Optional when exactly one account is connected."
```
- removedInput schema / properties / accountId / maxLength
```
Removed value: -512
```
- removedInput schema / properties / accountId / minLength
```
Removed value: -1
```
- removedInput schema / properties / accountId / type
```
Removed value: -"string"
```
- addedInput schema / properties / labels / description
```
Added value: +"Gmail labels or Outlook categories"
```
- removedInput schema / properties / labels / items / maxLength
```
Removed value: -512
```
- addedInput schema / properties / messageIds / description
```
Added value: +"Messages to change, up to 100 distinct IDs"
```
- removedInput schema / properties / messageIds / items / maxLength
```
Removed value: -512
```
- removedInput schema / properties / messageIds / maxItems
```
Removed value: -100
```

Changed1 schema field changedOct 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

AddedOct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare idempotent=true and destructiveHint=false, so the safety profile is carried by structured data. The description adds the useful Gmail-label/Outlook-category equivalence, but says nothing about behavior when a label isn't present, batch semantics, or permission needs.

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?

One short sentence, front-loaded with the verb and resource, with the cross-provider synonym clause attached efficiently. No wasted words.

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?

The tool is low-complexity, an output schema exists, and annotations plus a fully-described schema cover most needs. The description fills the one gap structured data can't express — that Outlook categories are the same target — making it sufficient for correct invocation.

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 all three parameters (labels, messageIds, accountId) including the 100-item cap and the single-account shortcut are already documented in the schema. The description adds nothing beyond that 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 (remove) and resource (labels/categories) on messages, and clarifies that Outlook categories are the same concept as Gmail labels. It doesn't explicitly name the inverse sibling add_labels, so differentiation is only implicit from the name.

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?

Usage is inferable — call it when a message should lose a label, and add_labels is the obvious counterpart — but the description never states when to use this versus alternatives, nor any prerequisites.

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

All Fluxmail Cloud tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?