Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

create_label

Create a new Proton label as an IMAP folder under Labels/ to organize messages; then assign it with add_label.

Instructions

Create a new Proton label (as an IMAP folder below 'Labels/').

Assign it afterwards with add_label. name e.g. 'Invoices' or already
'Labels/Invoices'.

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

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/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 the underlying storage mechanism (an IMAP folder under 'Labels/') and the two acceptable input forms, but says nothing about behavior on duplicate names, permission requirements, or whether creation is idempotent. That is meaningful context, but not enough for a mutation tool with zero annotation coverage.

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?

Two short sentences, front-loaded with the action and the routing hint, then the naming detail. Every clause adds information and nothing is padded.

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?

An output schema exists, so return values need no explanation, and for a one-required-parameter creation tool the description covers what is created, where it lives, how to name it, and what to call next. The only gap is duplicate-name and failure behavior, which is modest for a tool this simple.

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 schema documents the single parameter only as 'Name' with 0% description coverage, so the description must compensate. It does: 'name e.g. 'Invoices' or already 'Labels/Invoices'' clarifies that both a bare label and a pre-prefixed path are accepted, which the schema alone does not convey.

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?

Names a specific verb and resource ('Create a new Proton label') and immediately disambiguates the abstraction by stating it materializes as an IMAP folder below 'Labels/'. It also separates itself from the sibling add_label, which handles assignment rather than creation, so an agent can pick between them without opening either schema.

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 clear lifecycle context: create the label here, then 'Assign it afterwards with add_label', which tells the agent the correct follow-up tool. It stops short of explicit when-not guidance (e.g., what to do if the label already exists) or error/exclusion conditions, so it lands below the top band.

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