Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_delete_block_rule

Delete a standing email block rule to undo an overly broad block, such as one that blocked a domain used by a real correspondent.

Instructions

Delete a standing block rule — use this to undo a rule that turned out to be too broad (e.g. it blocked a domain a real correspondent also uses).

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

Input Schema

NameRequiredDescriptionDefault
ruleIdYes
accountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about whether deletion is permanent, whether it requires admin/account permissions, or what happens to messages already blocked by the rule. The word 'standing' hints the rule persists across future mail, but the consequences of removal are left implicit.

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?

A single front-loaded sentence with the verb and resource first and the rationale in a parenthetical. It is tight, though the example leans illustrative rather than adding operational detail.

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

Completeness2/5

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

With no annotations, no output schema, and two undocumented required parameters, the description is too thin for a destructive mutation tool. An agent cannot tell how to obtain a ruleId, whether the deletion is reversible, or what a successful response confirms.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions either required parameter. It does not explain that ruleId comes from email_list_block_rules or what accountId identifies, so an agent gets no help beyond the bare property names.

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 ('Delete a standing block rule'), which clearly separates it from the create/list block-rule siblings named in the catalog. It stops short of explicitly naming an alternative, 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 Guidelines4/5

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

Gives a concrete when-to-use scenario: undoing a rule that turned out to be too broad, with a worked example of a domain shared by a real correspondent. No when-not-use conditions or pointers to alternatives (e.g. listing rules first to find the ID) are given.

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