Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_list_forward_rules

List every standing forwarding rule on an email account, including rules created manually in Gmail or Outlook, to audit where mail is being sent or find a rule ID before deleting it.

Instructions

List every standing rule on an account that forwards mail to another address, including rules made by hand in Gmail or Outlook. Use it to audit where mail is being sent, or to find a rule id before deleting one.

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>"
    },
    "name": "email_list_forward_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; 'List' implies read-only and the hand-made-rules clause usefully discloses that externally created rules are included. It says nothing about permissions needed, ordering, pagination, or the shape of returned rule objects, leaving real gaps for a no-annotation tool.

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 sentences, zero filler, with the scope statement front-loaded and the usage/next-step guidance following. Every clause earns its place.

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

Completeness4/5

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

For a simple single-parameter read tool with no output schema, the definition covers what it returns conceptually, why to call it, and what to do with the result. The only notable omission is the expected format of accountId.

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?

Only one parameter (accountId) with 0% schema description coverage, so the description must compensate; it refers to 'an account' but never clarifies whether accountId is an internal id or an email address, which matters given email_list_accounts exists. Partial compensation only.

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 ('List every standing rule on an account that forwards mail to another address') and narrows scope to forwarding rules, which clearly separates it from email_list_block_rules and email_create_forward_rule. The clause about hand-made Gmail/Outlook rules further sharpens what counts as in-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?

Gives two concrete use cases: auditing where mail is being sent, and obtaining a rule id before deletion — the latter implicitly routes the agent to email_delete_forward_rule. It stops short of stating exclusions (e.g. that block rules live in a different tool), so it is strong but not exhaustive.

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