Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Manage Gmail Label

manage_gmail_label

Destructive

Create, update, or delete Gmail labels by specifying the user email and action, with optional color and visibility settings.

Instructions

Manages Gmail labels: create, update, or delete labels.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Label name. Required for create, optional for update.
`action`	Yes	Action to perform on the label.
`label_id`	No	Label ID. Required for update and delete operations.
`text_color`	No	Label text color as a hex string, e.g. "#ffffff". Set together with background_color. Same palette. On update, omitting both keeps the label's current color.
`clear_color`	No	On update, remove the label's current color. Cannot be combined with background_color or text_color.
`background_color`	No	Label background color as a hex string, e.g. "#fb4c2f". Set together with text_color; Gmail requires both. Gmail accepts only its own palette, and an unsupported value is rejected before the request. Colors apply to user labels, not system labels.
`user_google_email`	Yes	The user's Google email address. Required.
`label_list_visibility`	No	Whether the label is shown in the label list. Defaults to "labelShow" on create. On update, omitting it keeps the label's current setting.
`message_list_visibility`	No	Whether the label's messages are shown in the message list. Defaults to "show" on create. On update, omitting it keeps the label's current setting.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv1.28.0Sep 24, 2026

removedInput schema / properties / background_color / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / background_color / type
```
Added value: +"string"
```

removedInput schema / properties / label_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / label_id / type
```
Added value: +"string"
```
changedInput schema / properties / label_list_visibility / default
```
Previous value: -"labelShow"New value: +null
```

changedInput schema / properties / label_list_visibility / description

Previous value: -"Whether the label is shown in the label list."New value: +"Whether the label is shown in the label list. Defaults to \"labelShow\" on create. On update, omitting it keeps the label's current setting."

changedInput schema / properties / label_list_visibility / enum

Previous value: -[
-  "labelShow",
-  "labelHide"
-]New value: +[
+  "labelShow",
+  "labelShowIfUnread",
+  "labelHide"
+]

changedInput schema / properties / message_list_visibility / default
```
Previous value: -"show"New value: +null
```

changedInput schema / properties / message_list_visibility / description

Previous value: -"Whether the label is shown in the message list."New value: +"Whether the label's messages are shown in the message list. Defaults to \"show\" on create. On update, omitting it keeps the label's current setting."

removedInput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / name / type
```
Added value: +"string"
```

removedInput schema / properties / text_color / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / text_color / type
```
Added value: +"string"
```

Changed3 schema fields changedv1.26.0Sep 6, 2026

addedInput schema / properties / background_color

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Label background color as a hex string, e.g. \"#fb4c2f\". Set together with text_color; Gmail requires both. Gmail accepts only its own palette, and an unsupported value is rejected before the request. Colors apply to user labels, not system labels."
+}

addedInput schema / properties / clear_color

Added value: +{
+  "default": false,
+  "description": "On update, remove the label's current color. Cannot be combined with background_color or text_color.",
+  "type": "boolean"
+}

addedInput schema / properties / text_color

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Label text color as a hex string, e.g. \"#ffffff\". Set together with background_color. Same palette. On update, omitting both keeps the label's current color."
+}

Changed17 schema fields changedv1.0.1Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / action / description
```
Added value: +"Action to perform on the label."
```
removedInput schema / properties / action / title
```
Removed value: -"Action"
```

addedInput schema / properties / label_id / description

Added value: +"Label ID. Required for update and delete operations."

removedInput schema / properties / label_id / title
```
Removed value: -"Label Id"
```
addedInput schema / properties / label_list_visibility / description
```
Added value: +"Whether the label is shown in the label list."
```
removedInput schema / properties / label_list_visibility / title
```
Removed value: -"Label List Visibility"
```
addedInput schema / properties / message_list_visibility / description
```
Added value: +"Whether the label is shown in the message list."
```
removedInput schema / properties / message_list_visibility / title
```
Removed value: -"Message List Visibility"
```

addedInput schema / properties / name / description

Added value: +"Label name. Required for create, optional for update."

removedInput schema / properties / name / title
```
Removed value: -"Name"
```

removedInput schema / properties / service

Removed value: -{
-  "title": "service",
-  "type": "string"
-}

addedInput schema / properties / user_google_email / description
```
Added value: +"The user's Google email address. Required."
```
removedInput schema / properties / user_google_email / title
```
Removed value: -"User Google Email"
```

changedInput schema / required

Previous value: -[
-  "service",
-  "user_google_email",
-  "action"
-]New value: +[
+  "user_google_email",
+  "action"
+]

removedInput schema / title

Removed value: -"manage_gmail_labelArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.0Jun 10, 2025

TDQS

A3.5/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description adds little behavioral context. It repeats the operation types already present in the action enum but does not disclose side effects (e.g., deleting a label removes it from messages) or constraints (e.g., color pairing requirements) that are not already in the schema. With annotations covering the safety profile, the description's added value is minimal.

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?

The description is a single, well-structured sentence that front-loads the resource and operations. It contains no filler and every word contributes to understanding the tool's purpose.

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

Completeness3/5

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

The description is minimal, but the schema and annotations collectively cover the details: all parameters are described, destructive behavior is annotated, and an output schema exists. The description lacks explicit guidance on when not to use it, but given the richness of structured data, it is adequate though not exemplary.

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 coverage is 100% and the parameter descriptions are exceptionally detailed (e.g., background_color explains the Gmail palette restriction and pairing requirement). The tool description adds no parameter information beyond what the schema provides. According to the rubric, a baseline of 3 is appropriate when the schema does the heavy lifting.

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

Purpose5/5

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

The description states a specific verb ('manages') and resource ('Gmail labels'), and explicitly enumerates the three operations (create, update, delete). This clearly distinguishes it from siblings like list_gmail_labels (which lists) and manage_gmail_filter (which manages filters). It is not a tautology and conveys the tool's core function unambiguously.

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 – an agent can infer it is for creating/updating/deleting labels, not for listing them. However, it does not explicitly mention when not to use this tool or point to alternatives (e.g., 'to list labels, use list_gmail_labels'). The guidance is implied rather than explicit, so it falls short of a 4.

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

Deploy Server