Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_delete_forward_rule

Delete a standing email forwarding rule by account and rule ID to stop unwanted or obsolete forwards; no allowlist entry is required.

Instructions

Delete a standing forwarding rule by id. Needs no allowlist entry: stopping a forward is always allowed.

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_forward_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleIdYes
accountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.3/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, and it does add one valuable behavioral fact: no allowlist entry is required because stopping a forward is always allowed, which signals an asymmetric permission model. It omits whether deletion is idempotent, what happens when the ruleId does not exist, and whether the standing rule is removed immediately or queued.

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?

Two short sentences, purpose front-loaded, with the permission note immediately after. No filler or redundancy.

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?

For a simple two-parameter mutation with no output schema, the description covers the action and the permission precondition adequately. It is thin on the required accountId scope and on error/no-op behavior, which are the remaining things an agent needs to invoke it confidently.

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% for two required parameters. The phrase 'by id' loosely maps to ruleId, but accountId — required and undocumented anywhere — is never mentioned, so the description compensates for only half the gap.

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 forwarding rule by id' — which is clearly separable from email_create_forward_rule, email_list_forward_rules, and email_delete_block_rule. It does not name a sibling explicitly, so it stops short of full differentiation.

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 rather than stated: an agent infers it should call this when an existing forwarding rule must be removed, and the 'by id' phrasing hints the id comes from a listing call. There is no explicit when-to-use/when-not-to-use guidance and no named alternative such as email_delete for message deletion.

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