Skip to main content
Glama
codefuturist

Email MCP Server

by codefuturist

get_email

Read-only

Retrieve full email content by ID without altering read status. Options for plain text, removing quoted replies and signatures, and limiting size.

Instructions

Get the full content of a specific email by ID. Does NOT mark the email as seen (uses IMAP BODY.PEEK — non-destructive). Use format="text" to strip HTML, or format="stripped" to also remove quoted replies and signatures. Use maxLength to cap the body size for large emails. Set markRead=true only when you want to explicitly mark the email as read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoBody format: full=raw (default), text=plain text (strips HTML), stripped=plain text without quoted replies or signaturesfull
accountYesAccount name from list_accounts
emailIdYesEmail ID from list_emails or search_emails
mailboxNoMailbox path (default: INBOX)INBOX
markReadNoExplicitly mark the email as read after fetching (default: false — reading is non-destructive by default)
maxLengthNoTruncate body at this many characters. A hint shows how many characters remain.
Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint), the description specifies that it uses IMAP BODY.PEEK and does NOT mark as seen, and explains the non-destructive default behavior and the effect of markRead parameter.

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?

Three sentences, front-loading purpose and key behaviors, with efficient wording. Could be slightly more concise, but no unnecessary information.

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?

Covers key parameters and behavior adequately. No output schema, but description explains what is returned. Missing error handling or edge cases, but acceptable for this tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds extra value by explaining that 'stripped' removes quoted replies/signatures and that maxLength shows a hint with remaining characters.

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 clearly states the verb 'get' and resource 'email by ID', and distinguishes it from siblings like get_emails and get_email_status by specifying it retrieves full content with options for format and mark-as-read.

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?

Provides explicit guidance on when to use format options and maxLength, and when to set markRead=true. Does not explicitly state when not to use this tool relative to other email actions, but the context of siblings implies its read-only nature.

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

Install Server

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/codefuturist/email-mcp'

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