Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

read-mail-text

Read-only

Read up to 20 Microsoft 365 emails as cleaned text for triage, stripping padding, image placeholders, quoted replies, and tracking redirects.

Instructions

Triage view of up to 20 mail messages at once, as text with the bulk junk removed: invisible padding, image placeholders and quoted reply history (forwards keep theirs). Links are kept: Safe Links, Proofpoint and Google redirects are unwrapped to the real address and tracking parameters (utm_* and similar) dropped; only an address still over 300 characters (a tracking redirect) is shortened to ⟦link: domain⟧. Everything else (signatures, footers, whitespace) is left as the message has it; line endings become \n and ⟦ ⟧ in the body itself appear as [ ]. Use get-mail-message for the raw body or the quoted thread. Give messageIds (up to 20), or folderId with optional top and filter or search for the newest messages in a folder. Each message is cut to maxChars characters (default 3,000; marked truncated: true): pass a larger maxChars, up to 300,000, for the whole of a long message; a body over 300,000 characters is cleaned only that far. If the whole result would exceed the server limit (MS365_MCP_READ_MAIL_TEXT_MAX_CHARS, default 80000) the call fails, listing the largest messages, instead of returning part of it. Returns [{ id, from, to, cc, subject, received, hasAttachments, text, chars, truncated }].

Input Schema

NameRequiredDescriptionDefault
topNoWith folderId: how many messages, newest first (default and max 20).
filterNoWith folderId: OData $filter, e.g. receivedDateTime ge 2026-10-01T00:00:00Z or from/emailAddress/address eq 'a@example.com'.
searchNoWith folderId: KQL search, e.g. from:paul subject:"quarterly report" (quoting is normalised as for list-mail-messages). Graph cannot combine it with filter.
folderIdNoFolder to read from: a well-known name (inbox, sentitems, drafts, archive, deleteditems, junkemail) or a folder id.
maxCharsNoCut each message text to this many characters (marked truncated). Default 3,000; pass up to 300,000 for the whole of a long message (a body over 300,000 characters is cleaned only that far, also marked truncated).
messageIdsNoIds of the messages to read (max 20). Give messageIds or folderId, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.170.1

TDQS

A4.8/5.0
Behavior5/5

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

Even though annotations already declare readOnlyHint and openWorldHint, the description adds substantial undisclosed behavior: what is stripped (invisible padding, placeholders, quoted history), link unwrapping and the ⟦link: domain⟧ shortening, line-ending normalization, and the server-limit failure mode (MS365_MCP_READ_MAIL_TEXT_MAX_CHARS, default 80000) that fails the whole call rather than returning partial results.

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?

Front-loaded with purpose and cleaning behavior, then usage, then return shape; nearly every sentence earns its place. It is dense and long, but the length is carrying real behavioral information rather than filler.

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, cleaning rules, link handling, parameter semantics, the hard server-limit failure mode, and the exact return array shape, which matters since no output schema exists. Nothing needed to invoke it correctly is missing.

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 the baseline is 3, and the description still adds meaningful semantics: it explains the intent behind maxChars (default 3,000, up to 300,000, truncated flag), notes the server-wide cap that interacts with maxChars, and clarifies messageIds vs folderId exclusivity. It does not add syntax the schema lacks for filter/search, which cap it below 5.

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?

States a specific verb and resource ('Triage view of up to 20 mail messages at once, as text with the bulk junk removed') and precisely lists what is stripped versus retained. It distinguishes itself from the sibling get-mail-message, which it explicitly points to for the raw body or quoted 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?

Gives explicit selection criteria: 'Give messageIds (up to 20), or folderId with optional top and filter or search' for triage, and 'Use get-mail-message for the raw body or the quoted thread' for the alternative. The two modes of use and the exclusion are spelled out.

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