Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

remove_label

Removes a Proton label from one or more messages by UID while keeping the messages intact, so you can clean up labels without deleting mail.

Instructions

Remove a Proton label (uids = a single uid OR a list); the message itself is kept, no data loss.

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": "remove_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

B3.4/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 that only the label is removed and no message data is lost. It omits other behavioral facts an agent would want: permission requirements, whether removing a non-existent label errors, and whether the operation is idempotent.

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 clauses, front-loaded with the action and immediately followed by the key safety fact. Minor awkwardness from the line-broken formatting and parenthetical, but nothing extraneous.

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?

An output schema exists so return values need not be described, and the core behavior is covered. However, for a 3-param mutation tool with zero schema documentation, the unexplained folder parameter leaves a real gap in the definition.

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. It does add real value for two params — uids accepts a single uid or a list, and label accepts 'Important' or 'Labels/Important' — but the third parameter, folder, is never explained, and the interaction between folder and label removal is unclear.

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+resource ("Remove a Proton label") with clear scope, and the non-destructive guarantee distinguishes it from delete_email. It doesn't explicitly name the reverse sibling add_label, but the operation is unambiguous.

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 implied by the verb and by the contrast with deletion ("the message itself is kept"), but there is no explicit when-to-use/when-not guidance or reference to alternatives such as add_label or delete_email.

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