Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Delete mail rule

delete_mail_rule
Destructive

Deletes a persistent mail rule by ID so it stops applying to future incoming messages; actions already taken are not reverted.

Instructions

Delete a persistent mail rule by id so it stops applying to future incoming messages. Messages the rule already acted on are not reverted. To pause a rule instead of removing it, use update_mail_rule with enabled: false. Find the id with list_mail_rules.

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": {
      "ruleId": "<ruleId>"
    },
    "name": "delete_mail_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleIdYesThe id of the rule to delete, e.g. "rule-1a2b3c4d" — as returned by create_mail_rule or list_mail_rules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavioral context: the deletion affects only future matching, and messages already acted on are not reverted. It does not cover permission prerequisites or what happens on a repeat delete of the same id (relevant given idempotentHint=false), so it stops short of a 5.

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?

Four short sentences, front-loaded with the core action and non-reversibility, then alternatives, then id discovery. Nothing is padded and no sentence is redundant with another.

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 single-parameter destructive delete with no output schema, the description covers purpose, side-effect boundaries, an alternative tool, and id sourcing — everything an agent needs to call it correctly and safely.

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 coverage is 100% and the sole ruleId parameter is already documented with format and provenance in the schema itself. The description's 'Find the id with list_mail_rules' largely restates what the schema's description already says, so it adds little meaning beyond structured data — baseline 3 is correct.

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?

States a specific verb and resource ('Delete a persistent mail rule by id') plus the effect scope ('stops applying to future incoming messages'), which distinguishes it from update_mail_rule, preview_mail_rule, and list_mail_rules without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit alternative and the condition that selects it ('To pause a rule instead of removing it, use update_mail_rule with enabled: false') and routes the agent to list_mail_rules for id discovery. Both the when-to-use and when-to-use-something-else cases are covered.

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