Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_add_account

Add a new IMAP or iCloud email account with host, port, and credentials, so you can search, send, and organize mail. Gmail and Outlook require the OAuth setup wizard.

Instructions

Add a new IMAP or iCloud email account (Gmail and Outlook require the setup wizard for OAuth)

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": {
      "provider": "<provider>",
      "name": "<name>",
      "email": "<email>"
    },
    "name": "email_add_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
tlsNoUse TLS (default: true)
hostNoIMAP server hostname
nameYesDisplay name for the account
portNoIMAP server port (default: 993)
emailYesEmail address
passwordNoPassword or app-specific password
providerYesProvider type: "imap" or "icloud" (Gmail/Outlook require OAuth setup wizard)
smtpHostNoSMTP server hostname
smtpPortNoSMTP server port

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A3.7/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. It usefully discloses the OAuth provider restriction, but says nothing about whether the credentials are validated against the server at add time, whether failures roll back the account, or what the caller gets back — all important for a credential-storing mutation.

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?

One sentence, front-loaded with the action and resource, with the exclusion in parentheses so it reads as a qualifier rather than the main point. Nothing is wasted.

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 nine-parameter mutation that stores credentials with no annotations and no output schema, the description covers the biggest gotcha (OAuth providers) but leaves the agent guessing about validation behavior and results. It is adequate, not complete.

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%, so every parameter including host, port, TLS defaults, and app-specific passwords is already documented in the schema. The description adds only the provider restriction, which the schema's provider field already states, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ("Add a new IMAP or iCloud email account") and immediately scopes which providers are supported, which is far more than a restatement of the name. It stops short of differentiating from related siblings such as email_list_accounts or email_test_account, so an agent still has to infer where this fits in the account lifecycle.

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?

It gives an explicit when-not condition: Gmail and Outlook must go through the OAuth setup wizard instead. What's missing is the positive-path guidance — when to pick provider "imap" versus "icloud", and whether an account should be tested (email_test_account) after being added.

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