Skip to main content
Glama
gmail-mcp
by gchallen

create_label

Creates a Gmail label with optional nested path and color settings, automatically adding missing parent labels unless disabled.

Instructions

Create a label. Nested labels use "/" (Projects/Alpha); missing parents are created unless autoCreateParents is false. Color by preset name or by hex pair from Gmail's palette.

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": {
      "name": "<name>"
    },
    "name": "create_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
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 (LABEL_COLOR_PRESET_ prefix accepted).
backgroundColorNoHex color from Gmail's label palette, e.g. #fb4c2f. Arbitrary colors are rejected by Gmail.
autoCreateParentsNo
labelListVisibilityNoDefault labelShow.
messageListVisibilityNoDefault show.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description adds real value on top: missing parent labels are auto-created unless autoCreateParents is false, which is a side effect an agent must know before calling. It also warns that arbitrary colors are rejected by Gmail, though it does not describe permissions or the response.

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?

Three compact sentences, front-loaded with the core action and followed by the two non-obvious behaviors (nesting side effects, color input format). No filler, though the color sentence lightly restates what the schema already documents for colorPreset and backgroundColor.

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?

For a 7-parameter mutation tool with no output schema, the definition covers the risky behavior (implicit parent creation) and the fiddly input format (color). It omits what the call returns and any scoping/permission requirements, which leaves a small but real gap.

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

Parameters4/5

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

Schema coverage is 57%, so the description must compensate, and it does for the most important parameter: the undocumented `name` field gains meaning through the "/" nesting syntax (Projects/Alpha) and the autoCreateParents interaction. Color semantics are also tied to the two color parameters, though textColor and the visibility enums are left entirely to the schema.

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?

"Create a label" states a specific verb and resource, clearly distinct from siblings like update_label, delete_label, and get_label. It does not explicitly name or contrast an alternative, so it stops short of a 5.

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?

Usage context is implied rather than stated: the description explains how to nest labels and how colors work, but never says when to create versus update an existing label or check list_labels first. No exclusions or prerequisites are given.

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