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

Overview Schema Source Related Servers Score Discussions Admin

Manage Gmail Label

manage_gmail_label

Destructive

Create, update, or delete Gmail labels with color and visibility settings. Manage label organization directly from your AI assistant.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.	labelShow
`message_list_visibility`	No	Whether the label is shown in the message list.	show

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds the action types but does not disclose additional behavioral traits such as irreversibility of delete, dependency on label_id for update/delete, or color constraints (these are in the schema). It does not contradict annotations, but adds minimal context beyond them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the primary actions. There is no fluff, and it is appropriately sized for the tool's complexity. However, it lacks structured detail that could aid parsing.

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 has a rich input schema (100% coverage) and an output schema, so the description needn't explain return values. All parameter semantics and constraints are fully documented in the schema. The description, while minimal, does not omit anything critical when combined with the schema; an agent can call the tool correctly.

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%, with detailed descriptions for all nine parameters including enums and constraints (e.g., color palette, mutual exclusivity of clear_color). The description adds nothing beyond the schema, so the baseline of 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?

The description 'Manages Gmail labels: create, update, or delete labels' clearly identifies the resource (Gmail labels) and enumerates the three actions. It distinguishes from siblings like list_gmail_labels (read-only) and modify_gmail_message_labels (applies labels to messages), though it doesn't explicitly name alternatives. The verb 'Manages' is generic, but the colon clarifies the scope.

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?

No guidance is provided on when to use this tool versus siblings. There is no mention of alternatives such as list_gmail_labels for reading or modify_gmail_message_labels for message-label assignment, nor any exclusions. The agent must infer usage from the actions alone.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taylorwilsdon/google_workspace_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server