Skip to main content
Glama
marlonluo2018

Microsoft Graph MCP Server

get_email_content

Retrieve full email content including body, attachments, and metadata by cache number. Optionally download attachments to workspace.

Instructions

Get full email content by cache number. Use the cache number from browse_email_cache (e.g., 1, 2, 3) to retrieve complete email with body, attachments, and all details. Returns: {success: boolean, subject: string, from: string, to: array, cc: array, bcc: array, body: string, attachments: array, sent_date: string, received_date: string}. Note: Invalid cache_number returns appropriate error message. ATTACHMENT DOWNLOAD: Set download_attachments=true to download attachments to the workspace/attachments folder. Attachments are saved with their original names. Use attachment_names to download only specific attachments. IMAGE ATTACHMENTS: When an email has image attachments (contentType starts with 'image/'), image content will be included automatically for multimodal analysis (requires MULTIMODAL_SUPPORTED=true in config). IMPORTANT: If images appear in the response, you MUST analyze them immediately - they often contain critical information (screenshots, photos, diagrams, charts, instructions) not mentioned in the text body. Do NOT skip image analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
return_htmlNoIf true, return full HTML body. If false (default), return plain text body. Note: This only affects email body format, not image attachments.
cache_numberYesCache number from browse_email_cache (e.g., 1, 2, 3)
download_pathNoOptional custom path for downloading attachments. If not specified, defaults to workspace/attachments folder.
attachment_namesNoOptional list of specific attachment names to download. If not specified, downloads all non-inline attachments.
download_attachmentsNoIf true, download email attachments to the workspace/attachments folder. Default: false. Attachments will include 'downloaded' and 'file_path' fields in the response.
Behavior4/5

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

With no annotations, the description fully discloses return format, error behavior for invalid cache numbers, attachment download mechanics, and image handling requirements. It does not mention side effects but is transparent about read operations.

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?

The description is well-structured with clear sections for attachments and images, and the main purpose is front-loaded. While detailed, each part adds value, though some notes could be more concise.

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?

Given no output schema, the description fully defines the return object structure. It covers all five parameters with usage scenarios, error handling, and special cases like image attachments, making it complete for agent invocation.

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?

Despite 100% schema coverage, the description adds substantial context beyond the schema, including the relationship to browse_email_cache, download mechanics, image handling, and default paths. This significantly aids parameter understanding.

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 tool retrieves full email content using a cache number from browse_email_cache. It distinguishes itself by specifying it returns complete email details (body, attachments, etc.) unlike the sibling browse_email_cache.

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 instructs to use cache numbers from browse_email_cache and provides guidance on downloading attachments and image analysis. It lacks explicit when-not-to-use statements but gives sufficient context for typical usage.

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/marlonluo2018/microsoft_graph_mcp_server'

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