Skip to main content
Glama
SinoEdwards

Mail Agent MCP

by SinoEdwards

imap_update_account

Update an existing IMAP account to correct SMTP settings, credentials, or folder preferences without deleting and re-adding the account.

Instructions

Update an existing IMAP account. Useful for fixing SMTP settings without removing and re-adding the account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tlsNoUse TLS for IMAP
hostNoIMAP host
nameNoNew friendly name
portNoIMAP port
userNoIMAP username
emailNoEmail address (From: header)
passwordNoNew password
smtpHostNoSMTP hostname
smtpPortNoSMTP port (465 for SMTPS, 587 for STARTTLS)
smtpUserNoSMTP username (if different from IMAP user)
accountIdYesID of the account to update
defaultBccNoOptional BCC address(es) applied automatically to every outbound message for this account. Pass an empty string to clear
saveToSentNoSave sent emails to the Sent folder
sentFolderNoExplicit Sent-folder name for saving sent-mail copies (e.g. "Gesendet"). Overrides auto-detection; pass an empty string to clear the override and re-enable auto-detection. Check names with imap_list_folders
smtpSecureNoUse implicit TLS (SMTPS). Port 587/25 always use STARTTLS regardless
smtpPasswordNoSMTP password (if different from IMAP password)
Install Server

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only says 'update' and offers the SMTP-fix use case; it does not explain partial-update semantics, credential requirements, whether unmentioned fields are preserved, or any side effects of updating an account.

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?

The description is two sentences with no filler. The core action is front-loaded, and the second sentence adds a concrete motivating use case. Every word earns its place.

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?

The schema richly documents parameters such as smtpSecure behavior and sentFolder override semantics, so parameter context is strong. However, for a complex mutation tool with 16 parameters and no annotations or output schema, the description is thin on update behavior, idempotency, and what happens to fields not supplied.

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 description coverage is 100%, so the input schema already documents all 16 parameters in detail. The description adds no parameter-level meaning beyond pointing at SMTP settings, which is a subset of what the schema covers. Baseline 3 is appropriate.

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?

The description opens with a clear verb-resource pair, 'Update an existing IMAP account,' which precisely identifies the action and target. Describing it as useful for fixing SMTP settings helps distinguish it from imap_add_account and imap_remove_account without any ambiguity.

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?

The description explicitly frames this as the tool for changing settings on an existing account, especially SMTP configuration, and contrasts it with removing and re-adding the account. It does not explicitly name sibling tools or state when not to use it, so it falls just short of full alternative routing.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SinoEdwards/mail-agent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server