Skip to main content
Glama
gmail-mcp
by gchallen

update_label

Rename a Gmail label or update its text/background color and list visibility to organize messages and control how labels appear.

Instructions

Rename a label or change its color or visibility.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "labelId": "<labelId>"
    },
    "name": "update_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
labelIdYesLabel ID or exact current name.
textColorNo
colorPresetNoOne of: BLACK, DARK_GRAY, GRAY, LIGHT_GRAY, WHITE, RED, ORANGE, YELLOW, GREEN, MINT, TEAL, BLUE, PURPLE, PINK, DARK_RED, DARK_ORANGE, DARK_GREEN, DARK_BLUE, DARK_PURPLE, DARK_PINK, BROWN.
backgroundColorNo
labelListVisibilityNo
messageListVisibilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare that this is a non-read-only, non-destructive operation with open-world interaction. The description adds that the operation can rename or change color/visibility, which is useful scope, but it does not explain partial-update behavior, side effects, or whether unspecified fields are preserved.

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 front-loaded sentence with no wasted wording. Every phrase contributes directly to stating the tool's scope.

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

Completeness2/5

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

For a mutation tool with seven parameters, low schema coverage, and no output schema, the one-sentence description is too thin. It omits the required labelId, the distinction between the multiple color and visibility fields, and any indication of what the update returns or how unspecified fields behave.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 29% schema description coverage across seven parameters, the description does not adequately explain the parameters. It mentions name, color, and visibility at a high level, but it does not distinguish colorPreset from textColor and backgroundColor, nor does it clarify the two separate visibility parameters.

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 states a specific update action on a label and names the editable aspects: rename, color, and visibility. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as create_label or delete_label.

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 gives no explicit guidance on when to use this tool versus alternatives like create_label, delete_label, or label_message. It only implies that it is for modifying an existing label, with no exclusions or prerequisites stated.

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