Skip to main content
Glama
gmail-mcp
by gchallen

list_labels

Read-only

Retrieve every Gmail label with its ID, name, type, color, and visibility so you can identify system and user labels before applying them to messages.

Instructions

All labels with IDs, names, type (system or user), colors and visibility. System labels: INBOX, UNREAD, STARRED, IMPORTANT, SENT, DRAFT, TRASH, SPAM, CATEGORY_*. Label tools accept either an ID or an exact name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds real value beyond that by disclosing the shape of the results (IDs, names, system-vs-user type, colors, visibility) and enumerating the concrete system label set including the CATEGORY_* wildcard, which annotations cannot convey.

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 short, front-loaded sentences: what is returned, what the system labels are, and how label identifiers are accepted elsewhere. The system-label enumeration is long but earns its place by preventing an agent from guessing at IDs; nothing is redundant.

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?

There is no output schema, so the description carries the burden of describing return values, which it does by naming the returned fields. The enumeration of system labels and the ID-or-name convention make it complete for a zero-parameter read tool, with only ordering or pagination behavior left unstated.

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?

The tool takes zero parameters, which sets the baseline at 4. The trailing note about accepting an ID or exact name is not about this tool's inputs but usefully frames how downstream label tools consume the values this tool returns.

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 opens with a specific resource and enumerates the exact attributes returned (IDs, names, type, colors, visibility), so an agent knows this is a full label inventory rather than a filtered lookup. It does not explicitly name a sibling such as get_label to contrast against, so it falls just 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 is only implied: 'All labels' plus the note that 'Label tools accept either an ID or an exact name' hints that this is the way to discover those IDs before calling label_message or update_message_labels. There is no explicit when-to-use or when-to-prefer-get_label statement, so the agent must infer the workflow.

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