Skip to main content
Glama
Sign In
Outlook MCP

Outlook MCP

by lanSall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

outlook_list_emails

List recent emails from any mail folder, with options to filter by unread status and limit the count.

Instructions

List recent emails from a mail folder (default: inbox).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "outlook_list_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
folderNoMail folder id or well-known name: inbox, sentitems, drafts, deleteditemsinbox
unreadOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only mentions 'recent' and 'default: inbox' but omits ordering, pagination, filtering, or authentication implications. The tool's read-only nature is implied but not stated, and no caveats like rate limits or response size are disclosed.

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?

The description is a single, crisp sentence without filler. It efficiently communicates the core function and default folder, earning its place with zero waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has three parameters, no output schema, and no annotations, yet the description explains none of the parameters beyond folder and provides no return format details. Given the moderate complexity, the description is too sparse; it does not explain the effects of 'top' or 'unreadOnly', nor when to use this over search.

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

Parameters2/5

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

Schema description coverage is only 33% (only folder is described). The tool description does not clarify the 'top' or 'unreadOnly' parameters, nor does it elaborate on folder values beyond what the schema already says. It adds minimal semantic value beyond the schema.

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?

The description clearly states the verb 'list' and the resource 'recent emails' within a mail folder, defaulting to inbox. It distinguishes itself from sibling tools like outlook_get_email (single email) and outlook_search_emails (search-based).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage for viewing recent emails in a folder, but provides no explicit guidance on when to choose this instead of search_emails or get_email. No exclusions or alternative scenarios are mentioned.

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