Local MCP

Microsoft 365 List Emails

m365_list_emails

Read-only

Use this when the user wants their Microsoft 365 / Outlook / Exchange inbox via the cloud — requires a connected M365 account (connect_m365_account). Returns subject, sender, date, and preview. For mail already in the Mac's Mail.app (including an Exchange account added there), use list_emails.

Input Schema

Name	Required	Description
`limit`	No	Number of emails to return (default 20, max 50)
`since`	No	Only emails received at or after this time: an ISO 8601 date (local midnight, e.g. '2026-10-24') or date-time (e.g. '2026-10-24T08:00:00', local unless it has a zone). Optional.
`folder`	No	Folder to list: inbox (default), sentitems, drafts, deleteditems, junkemail, archive, or any folder by its id, name or path from m365_list_email_folders.
`account`	No	Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.
`unread_only`	No	If true, return only unread emails

Output Schema

Name	Required	Description
`count`	No
`emails`	No
`account`	No	The email (UPN) of the Microsoft 365 account this call used.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / since

Added value: +{
+  "description": "Only emails received at or after this time: an ISO 8601 date (local midnight, e.g. '2026-10-24') or date-time (e.g. '2026-10-24T08:00:00', local unless it has a zone). Optional.",
+  "type": "string"
+}

Changed1 schema field changedOct 24, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +50
```

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / folder / description

Previous value: -"Folder name: inbox (default), sentitems, drafts, deleteditems"New value: +"Folder to list: inbox (default), sentitems, drafts, deleteditems, junkemail, archive, or any folder by its id, name or path from m365_list_email_folders."

addedOutput schema / properties / emails / items / properties / conversation_id

Added value: +{
+  "description": "For m365_move_email (conversation_id).",
+  "type": "string"
+}

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / account

Added value: +{
+  "description": "Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.",
+  "type": "string"
+}

addedOutput schema / properties / account

Added value: +{
+  "description": "The email (UPN) of the Microsoft 365 account this call used.",
+  "type": "string"
+}

First observedJun 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description still earns credit for disclosing the auth prerequisite (a connected M365 account) and the shape of what comes back (subject, sender, date, preview), which helps confirm this is a read of remote data rather than a local cache.

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 selection condition and followed by the disambiguation to the sibling. Nothing repeated from the schema and no 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?

Given an output schema, the return-value description is optional but harmless; combined with the auth prerequisite and the sibling routing, an agent has everything needed to call this correctly and avoid the local-Mail.app confusion.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema itself explains limit, since, folder enum-like values, account resolution, and unread_only in detail. The description adds no parameter guidance beyond implying the account prerequisite, so the baseline 3 applies.

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 resource and channel: the user's Microsoft 365 / Outlook / Exchange inbox accessed via the cloud, and names the return payload. It explicitly distinguishes itself from list_emails, which serves Mail.app, so an agent can pick between the two without opening a schema.

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 an explicit when-to-use condition (user wants cloud M365/Outlook/Exchange mail) and an explicit when-not case with the alternative named ('mail already in the Mac's Mail.app ... use list_emails'). Prerequisite connect_m365_account is also called out.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.