Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

add_label

Apply a Proton label to one or more messages by UID while keeping them in their current folder; use it to organize mail without moving it.

Instructions

Add a Proton label (uids = a single uid OR a list); the message stays in its folder and is NOT moved (compare move_email).

label e.g. 'Important' or 'Labels/Important'.

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": {
      "uids": "<uids>",
      "label": "<label>"
    },
    "name": "add_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidsYes
labelYes
folderNoINBOX

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/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 and does disclose the key behavioral trait: the message is not moved out of its folder, so the operation is additive rather than relocating. It leaves out whether the label must pre-exist (vs. being created), whether repeated calls are idempotent, permission/auth requirements, and any error behavior; return values are covered by the output schema.

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?

Two short lines, front-loaded with the action and immediately followed by the argument semantics and the sibling contrast; there is no filler. The unusual line breaking and trailing quote are cosmetic noise but do not obscure the content.

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 simple three-parameter mutation with an output schema, the description covers the action, the uids semantics, the label format, and the non-move behavior. The unaddressed folder parameter and the absence of guidance on label existence or idempotency keep it from being fully complete for an annotation-free tool.

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 description coverage is 0%, so the description must compensate, and it does for two of three parameters: uids accepts one integer or a list, and label uses forms like 'Important' or 'Labels/Important'. The folder parameter (default INBOX) is never mentioned, leaving its meaning entirely to the bare schema title.

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 states a specific verb and resource ("Add a Proton label") and immediately clarifies the shape of its main argument (uids = a single uid OR a list), which the schema does not express beyond anyOf. It also names and distinguishes itself from the move_email sibling, so an agent can tell the two apart without opening schemas.

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?

It gives a clear usage signal with the contrast "the message stays in its folder and is NOT moved (compare move_email)", which effectively routes the agent between add_label and move_email. It does not cover other cases, such as whether labels must already exist (create_label) or how this differs from apply_filters, but the core when-to-use is explicit.

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