Skip to main content
Glama
mpalermiti

outlook-mcp

by mpalermiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

outlook_read_messages

Read-only

Bulk-read up to 20 Outlook messages by ID in one batch call and return per-message results plus failures, so you can avoid multiple single-message reads.

Instructions

Bulk read up to 20 messages by ID via $batch — use NOT N outlook_read_message calls.

Per-message shape in messages matches outlook_read_message byte-for-byte for the same (format, concise, include_deferred_send, include_sender_auth). Ordering follows input message_ids. Returns {messages, failures, requested, succeeded, failed} — 404s on some IDs are surfaced in failures without failing the whole call (partial-failure tolerant).

Example: outlook_read_messages(message_ids=[id1, id2, id3], concise=True) Hard cap of 20 (Graph $batch limit).

Input Schema

NameRequiredDescriptionDefault
formatNotext
conciseNo
message_idsYes
include_sender_authNo
include_deferred_sendNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.30.2
    • removedInput schema / properties / concise / title
      Removed value: -"Concise"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / include_deferred_send / title
      Removed value: -"Include Deferred Send"
    • removedInput schema / properties / include_sender_auth / title
      Removed value: -"Include Sender Auth"
    • removedInput schema / properties / message_ids / title
      Removed value: -"Message Ids"
    • removedInput schema / title
      Removed value: -"outlook_read_messagesArguments"
  2. Changed1 schema field changedv1.28.0
    • addedInput schema / properties / include_sender_auth
      Added value: +{
+  "default": false,
+  "title": "Include Sender Auth",
+  "type": "boolean"
+}
  3. Addedv1.14.0
  4. Removedv1.12.0
  5. First observedv1.11.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses partial-failure behavior: 404s are surfaced in failures without failing the whole call. It also specifies ordering, return keys, and the batch size cap, which are useful operational traits.

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?

It is front-loaded with the core bulk-read behavior, then adds ordering, return shape, partial-failure semantics, and an example without wasting space. The structure supports quick scanning and the example is directly useful.

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 batch read tool with no output schema, it explains the return envelope and partial-failure behavior well. It is not fully complete because the optional parameters remain opaque at 0% schema description coverage, relying on the sibling read tool for their meaning.

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 0%, so the schema itself documents none of the five parameters. The description clarifies message_ids, cap, and ordering, and says the optional flags mirror outlook_read_message, but it does not explain format values, what concise changes, or what the two include flags include.

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: bulk-read messages by ID via $batch. It also explicitly distinguishes itself from the sibling outlook_read_message by telling the agent to use this instead of N single-message calls.

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?

The description names the intended use case (reading multiple messages by ID), the alternative to avoid (N outlook_read_message calls), and the hard cap of 20. That is enough for an agent to select this tool correctly when it already has IDs.

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