Skip to main content
Glama
jopmiddelkamp

outlook-mcp-limited

by jopmiddelkamp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_emails

List emails from a folder with filters for sender, date, unread. Returns JSON summaries; use read_email with ID for full content.

Instructions

List emails from a mail folder with optional filters (sender substring, date range, unread-only). Returns a compact JSON array of message summaries. Use read_email with a returned id to fetch full content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoFilter: only emails whose sender address STARTS WITH this value (case-sensitive, Graph OData limitation). For a full domain match use 'user@acme.com' or 'acme.com'. For fuzzy / case-insensitive matching use the search_emails tool instead.
limitNoMaximum number of emails to return. Default 25, max 100.
sinceNoFilter: only emails received at or after this ISO-8601 timestamp (e.g. 2026-04-15T00:00:00Z).
untilNoFilter: only emails received strictly before this ISO-8601 timestamp.
folderNoMail folder to list. Defaults to 'inbox'. Either a well-known name (inbox, drafts, sentitems, deleteditems, junkemail, archive, outbox, conversationhistory) or a folder ID returned by list_folders. Unknown names produce a 404 from Graph — use list_folders to discover custom folders.
unreadOnlyNoIf true, return only unread messages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return shape ('compact JSON array of message summaries'), but omits pagination behavior, permission/auth requirements, and whether an empty folder returns an empty array or an error.

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?

Three short sentences, front-loaded with the primary action, then filters, then the return format and follow-up call. Every sentence earns its place with no padding.

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 six-parameter, filter-based list tool with no output schema and no annotations, the description covers purpose, filtering scope, return shape, and the next step in the workflow. Remaining gaps (pagination, auth, empty-result behavior) are modest for a read-only lister.

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%, so the schema already documents all six parameters thoroughly (defaults, max, ISO-8601 format, folder names, 404 behavior). The description's paraphrase ('sender substring') is actually looser than the schema's precise 'STARTS WITH' semantics, adding no meaning beyond it.

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 ('List emails from a mail folder') plus the scope of optional filters, and names the sibling tool (read_email) that handles full content. An agent can distinguish it from read_email and search_emails 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 Guidelines4/5

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

Explicitly routes in the retrieval workflow: use read_email with a returned id to fetch full content, which clarifies that this tool yields summaries, not bodies. It stops short of an explicit when-to-use-this vs search_emails rule (that guidance only lives in the schema for the 'from' parameter).

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

Install Server

Other Tools