Skip to main content
Glama
yu2001-s
by yu2001-s

get-message

Retrieve the full content of a specific email message by its ID, including subject, body (plain text or HTML), and RFC message ID. Provide mailbox and account for faster access in large folders like Sent Items.

Instructions

Use when: reading the full body of one message whose id you already have (numeric or imap:…); set preferHtml to get the HTML body instead of plain text. Returns: the message subject, body (plain text by default, HTML when preferHtml is true), and its stable RFC Message-ID (rfcMessageId) for dedup/threading. Tip: pass the mailbox+account you got the id from (e.g. from search-messages) to fetch it directly — required for reliable reads of large folders like "Sent Items", which otherwise time out. Do not use when: you don't yet have an id (use search-messages or list-messages first), or you want the whole conversation (use get-thread).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
accountNoAccount that holds the message. Pair with `mailbox` for a direct, scan-free fetch.
mailboxNoMailbox that holds the message (e.g. "Sent Items"). Numeric ids are unique per mailbox; supplying this (with account) opens that mailbox directly instead of scanning every mailbox, which is required to read large folders like Sent Items without timing out.
preferHtmlNoReturn the HTML body (extracted from the message source) instead of plain text

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
bodyNo
isHtmlNo
subjectNo
rfcMessageIdNoStable RFC 5322 Message-ID (angle brackets stripped); empty when the message has none
Behavior5/5

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

Describes return fields (subject, body, rfcMessageId), the effect of preferHtml, and reliability requirements for large folders, despite no annotations.

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?

Front-loaded with 'Use when', then returns, tip, and 'Do not use'. Every sentence is necessary and well-structured.

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

Completeness5/5

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

Covers purpose, usage, parameter nuances, return format, and exclusions. With output schema present, it is fully complete.

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

Parameters5/5

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

Adds important meaning beyond schema: id format, mailbox+account requirement for large folders, and preferHtml behavior.

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?

Clearly states the tool reads the full body of one message given an ID, distinguishing it from search-messages and get-thread.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (reading a message by ID) and when not to use (without an ID or wanting a conversation), with a tip for large folders.

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/yu2001-s/apple-mail'

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