Gmail MCP Server

by neutral-Stage

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

create_label

Create a new Gmail label to organize emails. Supports nested folders and custom visibility settings.

Instructions

Create a new Gmail label (folder).

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

Name	Required	Description	Default
`name`	Yes	Label name (use / for nesting, e.g. 'Work/Invoices')
`messageListVisibility`	No	Whether to show in message list	show
`labelListVisibility`	No	Whether to show in label list	labelShow

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jun 21, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided; description lacks disclosure of behavioral traits such as duplicate label handling, naming conventions beyond schema, or permission requirements.

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?

Single concise sentence; efficient but could benefit from a slightly fuller description of usage context.

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?

Simple tool but missing information about behavior on duplicate label creation, label limits, or output. Adequate for minimal viability.

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% with parameter descriptions; the description adds minimal value ('folder') but not beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a new Gmail label (folder)' using a specific verb and resource, and distinguishes from siblings like 'delete_label' and 'list_labels'.

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?

No guidance on when to create a label versus using alternatives like filters, or any prerequisites or restrictions.

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