Skip to main content
Glama
dipseth

google-workspace-unlimited

Manage Gmail Label

manage_gmail_label
Destructive

Create, update, or delete Gmail labels for one or multiple users. Supports single and batch operations with color and visibility settings.

Instructions

Manage Gmail labels: create, update, or delete labels. Supports single or multiple label operations using lists or JSON strings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoLabel name(s) - REQUIRED for CREATE. Single: 'My Label' or Multiple: ['Label1', 'Label2'] or JSON string
actionYesAction to perform: 'create' (requires name), 'update' (requires label_id), 'delete' (requires label_id)
label_idNoLabel ID(s) - REQUIRED for UPDATE/DELETE. Single: 'Label_123' or Multiple: ['Label_1', 'Label_2'] or JSON string
text_colorNoText color(s) - hex codes (e.g., '#ff0000'), color names (e.g., 'red'), auto-corrected to closest Gmail color. Single value, list, or dict mapping
background_colorNoBackground color(s) - hex codes (e.g., '#ffffff'), color names (e.g., 'white'), auto-corrected to closest Gmail color. Single value, list, or dict mapping
user_google_emailNoUse 'me' or 'myself' for auto-resolution to authenticated user, or provide specific email address. If None, uses current authenticated user (auto-injected by middleware).
label_list_visibilityNoLabel visibility in Gmail sidebar: 'labelShow' or 'labelHide'. Can be single value or list for multiple labelslabelShow
message_list_visibilityNoMessage visibility in conversations: 'show' or 'hide'. Can be single value or list for multiple labelsshow

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if operation failed
actionYesAction performed: 'create', 'update', or 'delete'
resultsYesStatus messages for each label operation (e.g., 'Created label: MyLabel (ID: Label_123)')
successYesWhether the operation completed successfully
userEmailYesEmail of the authenticated user
labels_processedYesNumber of labels that were processed in this operation
color_adjustmentsNoColor correction messages when requested colors were adjusted to nearest Gmail-supported colors
Behavior3/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false; description adds support for multi-format input and color auto-correction, but doesn't fully detail side effects beyond deletion.

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?

Description is very concise with two focused sentences, no wasted words, though could benefit from bullet points for scanability.

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?

With 8 parameters, full schema coverage, and an output schema, the description is adequate but lacks details on error handling, prerequisites, and behavior for edge cases like system 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 coverage is 100% with descriptions; description adds holistic context about multi-format support, but doesn't significantly extend individual parameter meaning.

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?

Description clearly states the tool manages Gmail labels with specific actions (create, update, delete) and supports multiple operations, distinguishing it from sibling tools like list_gmail_labels.

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?

No explicit guidance on when to use vs alternatives; the action enum provides some direction but lacks context like prerequisites or comparisons to related tools.

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

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/dipseth/google_workspace_fastmcp2'

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