Skip to main content
Glama
gmail-mcp
by gchallen

delete_label

Destructive

Delete a Gmail user label while preserving messages and their other labels; system labels cannot be deleted.

Instructions

Delete a user label. Messages keep their other labels. System labels cannot be deleted.

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": "delete_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelIdYesLabel ID or exact name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A4/5.0
Behavior4/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 covered. The description adds genuinely useful behavior beyond that: the blast radius is limited to the label, messages retain their other labels, and system labels are refused. It does not state whether deletion is permanent or reversible, which keeps it below a 5.

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?

Three short sentences, front-loaded with the action, then the side effect, then the constraint. Every sentence carries distinct information with no filler.

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 one-parameter destructive tool with no output schema, the description covers what is removed, what survives, and what is prohibited. The only meaningful omission is confirmation of irreversibility or required permissions, which the destructive annotation partially implies.

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% and the single labelId parameter is fully documented as "Label ID or exact name." The description adds no further meaning about the identifier, so the baseline of 3 applies.

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?

States a specific verb and resource ("Delete a user label") and narrows scope to user labels, which distinguishes it from label-mutation siblings like create_label/update_label and from unlabel_message. It stops short of naming a sibling, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides a clear when-not condition ("System labels cannot be deleted"), which prevents the most likely erroneous call. It does not point to an alternative when the agent actually wants to detach a label from messages, but the usage context for the delete itself is clear.

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