Skip to main content
Glama
mail-mcp-server

mail-mcp-server

update_label

Rename a Gmail label or update its background and text colors together without changing any messages.

Instructions

Rename a label, or recolor it (background_color and text_color together, from Gmail's palette). Changes no message.

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": {
      "mailbox": "<mailbox>",
      "label": "<label>"
    },
    "name": "update_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
labelYes
mailboxYesA connected mailbox address (see list_mailboxes)
text_colorNo
background_colorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the operation changes no message and that colors come from Gmail's palette and must be paired, but it omits permissions, reversibility, and response behavior.

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 efficient sentence with the main action front-loaded and no wasted wording. The color pairing constraint is placed where it is immediately useful.

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?

For a mutation tool with no annotations and no output schema, the description includes an important side-effect note and color pairing rule. It remains incomplete because it does not cover required mailbox handling, optional fields, permissions, or expected return behavior.

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 description coverage is only 20%, so the description must compensate. It partially does so by implying that name is the new label name, label is the target, and the two color parameters must be used together from Gmail's palette, but it does not explicitly map every parameter or explain optionality.

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 uses a specific verb and resource: rename a label or recolor it. It clearly conveys the operation's scope, including that message contents are not changed, but it does not explicitly differentiate itself from siblings such as create_label or plan_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied for modifying an existing label, and the recolor case notes that background_color and text_color must be supplied together. However, it gives no explicit when-to-use versus alternatives and does not clarify whether name or color parameters are optional.

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