outlook-local-mcp

Overview Schema Source Related Servers Discussions Admin

recent_emails

Read-only

List recent Outlook emails newest-first from an inbox or folder, without bodies, and page through results with a cursor to review beyond the default 20 items.

Instructions

List recent emails, newest received first, without bodies. Defaults to the default Inbox. Call directly; no discovery is needed. Prefer the default 20-item page for overviews. store_id alone selects that store's Inbox; folder_id requires store_id. Follow next_cursor with unchanged filters (limit may change). Pagination is best effort, not a snapshot. Cursors are single-use and expire after 10 minutes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`store_id`	No
`folder_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`omitted`	No
`coverage`	Yes
`store_id`	Yes
`warnings`	No
`folder_id`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.2.1Sep 12, 2026

addedOutput schema / $defs / EmailSummary / properties / categories

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Categories"
+}

addedOutput schema / $defs / EmailSummary / properties / conversation_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Conversation Id"
+}

addedOutput schema / $defs / EmailSummary / properties / importance

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "low",
+        "normal",
+        "high"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Importance"
+}

First observedv0.1.0Sep 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already cover the read-only safety profile, but the description adds substantial operational context a caller cannot infer: cursors are single-use and expire after 10 minutes, pagination is best-effort rather than a snapshot, and next_cursor must be followed with unchanged filters. These are meaningful traits beyond the structured fields.

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?

Well front-loaded: purpose first, then usage guidance, then parameter and pagination rules. Seven sentences is dense but each one carries distinct information; no filler is present.

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?

With an output schema already present, return values need no explanation, and the description covers defaults, filter dependencies, and pagination lifecycle sufficiently for correct invocation. Nothing an agent needs to call the tool 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 description coverage is 0%, so the description must carry the semantics, and it does: store_id alone selects a store's Inbox, folder_id requires store_id, cursor drives pagination, and limit's default of 20 is flagged. Cursor format and exact id semantics remain unstated, keeping it below a 5.

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?

States a specific verb and resource ("List recent emails") with scope and ordering detail ("newest received first, without bodies") and a default target ("Defaults to the default Inbox"). This implicitly separates it from read_email (no bodies) and search_emails (recent, not search), but it never names a sibling, so it falls short of full differentiation.

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?

"Call directly; no discovery is needed" and "Prefer the default 20-item page for overviews" give clear when-to-use context for the default and paged cases. It does not explicitly compare against search_emails or read_email as alternatives, so there are no stated exclusions.

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

Deploy Server