Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

delete_filter

Removes an existing sender filter using the exact from address and leaves current messages untouched; identify the filter term with list_filters.

Instructions

Remove a sender filter (existing messages stay untouched).

Args:
    from_address: The exact filter term from list_filters.

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": "delete_filter"
  }
}

Input Schema

NameRequiredDescriptionDefault
from_addressYes

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 behavioral burden, and it does disclose one important trait: deleting a filter does not affect already-received messages. It is silent on whether the removal is reversible, whether it requires confirmation or elevated permissions, and what happens if from_address matches nothing.

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?

The first sentence is front-loaded and tight, and the Args block is minimal. The docstring-style parameter restatement is slightly redundant but costs little for a single-parameter tool.

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 explained, and the tool is simple. Still, for a mutation with zero annotations, the definition should at minimum state the error/idempotency behavior when the filter term is absent or mistyped.

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 schema adds nothing about from_address. The description partially compensates by saying it is an "exact filter term from list_filters," communicating that it is an exact-match string rather than a free-form address, but it does not clarify whether it accepts an address, a display name, or a full filter expression.

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 ("Remove a sender filter") and immediately scopes the effect with "existing messages stay untouched," which distinguishes it from message-level operations in the sibling set. It does not explicitly name list_filters/create_filter as the contrasting tools, but the operation itself 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?

The line "The exact filter term from list_filters" implies you should call list_filters first to obtain the value, which is a useful workflow hint. However, it never states when to use this versus create_filter or unsubscribe_sender, nor what to do if no matching filter exists.

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