Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

create_filter

Create a sender filter that matches an address or domain and labels, archives, marks read, marks spam, or trashes messages on each sweep; optionally apply it to the INBOX now.

Instructions

Create a sender filter (applied by this server, NOT a real Proton Sieve filter). Only with apply_now=True is it applied to the INBOX right away (default: no).

Matching messages (From contains from_address; a domain or address works
best) are handled on each sweep. action: label (default), archive, spam,
read or trash (only when explicitly wanted). 'label' is non-destructive
(COPY to Labels/Filter/<term>, the message stays in the inbox) - the safest
level for fuzzy names. Protected senders are never touched.

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": {
      "from_address": "<from_address>"
    },
    "name": "create_filter"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNolabel
apply_nowNo
from_addressYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.7/5.0
Behavior5/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 so well: it discloses that filters are re-evaluated 'on each sweep', that matching is 'From contains from_address', that 'label' performs a non-destructive COPY to Labels/Filter/<term> leaving the message in the inbox, and that protected senders are never touched. These are substantive behavioral facts an agent could not infer otherwise.

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?

Content is front-loaded with the core caveat and the apply_now condition before the matching and action details, and nearly every clause earns its place. The prose is slightly dense with stacked parentheticals, which costs some readability against a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter write tool with no annotations, the definition covers what is created, when it takes effect, how matching works, what each action does to the message, and the protected-sender safety net. An output schema exists, so return values need not be explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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: from_address matching semantics ('From contains from_address; a domain or address works best'), the full action vocabulary with default and per-value consequences, and apply_now's default of false. All three parameters gain meaning beyond the bare schema titles.

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 opens with a specific verb plus resource, 'Create a sender filter', and immediately disambiguates the concept by stating it is applied by this server and is NOT a real Proton Sieve filter. An agent knows exactly what object is being created and its scope.

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 states the activation condition clearly ('Only with apply_now=True is it applied to the INBOX right away (default: no)') and guides action selection, flagging archive/spam/read/trash as 'only when explicitly wanted' and recommending 'label' as the safest choice for fuzzy names. It does not reference sibling tools like list_filters or delete_filter, but the when-to-use guidance within the tool is explicit.

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