Skip to main content
Glama
mail-mcp-server

mail-mcp-server

create_label

Creates a label in a connected mailbox, optionally nested using Parent/Child, without changing any messages; returns an existing label unchanged.

Instructions

Create a label (use "Parent/Child" to nest). Changes no message. A label that already exists is returned as it is.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
mailboxYesA connected mailbox address (see list_mailboxes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations present, the description does meaningful work: it discloses that the operation touches no messages (non-destructive to mail) and that duplicate creation is idempotent, returning the existing label. It omits permission requirements and the exact return shape, but the safety-relevant behavior is covered.

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 clauses, front-loaded with the action, each carrying distinct information (nesting format, message neutrality, idempotency). No filler or redundancy.

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 two-parameter creation tool with no output schema and no annotations, the definition covers the essentials an agent needs to invoke it correctly. It stops short of describing what the returned label looks like or any constraints on label names.

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 50%: `mailbox` is documented in the schema via list_mailboxes, while `name` is a bare string. The description compensates for the undocumented parameter by explaining the "Parent/Child" path format, which is genuine meaning beyond the schema, but adds nothing about mailbox selection.

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 ("Create a label") and immediately scopes it with nesting syntax and idempotent semantics. It is clearly distinguishable from the update/delete label siblings, though it never names an alternative explicitly.

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?

No direct when-to-use/when-not guidance or pointers to update_label for renaming. However, "A label that already exists is returned as it is" does give practical guidance that the agent need not pre-check existence before calling, which is real usage value.

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