Fluxmail

Remove labels

remove_labels

Idempotent

Remove Gmail labels or Outlook categories from selected messages by specifying message IDs and labels, enabling cleanup of message organization across connected accounts.

Instructions

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.

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 / 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
```

Addedv0.16.0Oct 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description need not restate it. The description adds only the Outlook-category synonym and target context, but does not explain behavior when labels are absent or message IDs are invalid.

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, front-loaded sentence with no filler. It immediately states the action and resource.

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 simple, annotations cover safety and idempotency, the input schema is fully described, and an output schema exists. The description is complete enough for invocation, though it could have added minor routing context against add_labels.

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 parameters are documented in the input schema. The description mentions labels and messages but adds no syntax, format, or constraints beyond what the schema already provides; baseline 3 applies.

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, or Outlook categories") plus the target ("messages"). It is clearly distinguishable from add_labels, though it does not explicitly name sibling alternatives.

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?

The description offers no explicit guidance on when to use this tool versus alternatives such as add_labels, nor does it state prerequisites or exclusions. Usage is only implied by the verb "Remove".

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