Skip to main content
Glama

Read Email Message

get_message
Read-only

Retrieve a specific Microsoft 365 email with full body content, optionally as plain text to strip HTML/CSS and reduce payload size.

Instructions

Get a specific email message with full body content. Pass body_format:'text' for marketing or newsletter mail — Graph converts server-side, avoiding tens of thousands of characters of HTML and CSS.

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": {
      "message_id": "<message_id>"
    },
    "name": "get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNoEmail address of another mailbox to act on (delegated or shared), e.g. 'someone@example.com'. Omit for your own mailbox; required when this server signs in as an application. Only addresses this server is configured to allow will be accepted.
message_idYesThe message ID, or a short ref returned by scan_messages
body_formatNoBody format to request. 'text' strips HTML/CSS server-side. Default: the message's own format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true is consistent with a read operation, so the description need not restate safety. It does add genuine behavioral context: the call returns the full body, and text format is converted server-side by Graph, avoiding tens of thousands of characters of HTML/CSS — useful for predicting response size. It omits error behavior for a missing message and delegated-mailbox auth implications, which the schema partially covers.

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?

Two sentences, front-loaded with the core action, and the second sentence is a concrete, non-redundant usage tip. No filler or restatement of the name/title.

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?

For a 3-parameter read-only tool with no output schema, the description covers purpose and the one non-obvious parameter tradeoff, which is enough to call it correctly. Minor gaps remain around what 'full body content' includes (headers, attachments) and failure modes, but nothing blocking.

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, but the description adds real meaning beyond the schema for body_format by explaining the cost/benefit of choosing 'text' (server-side conversion, large payload avoidance) for marketing/newsletter mail. It says nothing extra about mailbox or message_id beyond the schema.

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 ('Get a specific email message with full body content'), which cleanly separates it from write/send siblings and from other get_* resources like get_contact or get_event. It does not explicitly name a sibling it replaces, so it falls just short of a 5.

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

Usage Guidelines3/5

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

Usage guidance is limited to the body_format choice ('Pass body_format:'text' for marketing or newsletter mail'), which is really parameter-level advice. There is no explicit when-to-use-this-vs-alternative framing, e.g., pointing to scan_messages first to obtain an ID (that hint lives only in the schema).

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

Deploy Server

Other Tools