Skip to main content
Glama
hasan-imam

mcp-outlook-applescript

by hasan-imam

list_emails

List email summaries from a specified Outlook folder, ordered newest first, with a 500-character body preview. Supports pagination and date filters for browsing.

Instructions

List email summaries in a specific mail folder, ordered newest first. Each result includes a 500-char body preview for browsing without needing get_email. Returns {items, count, hasMore} — when hasMore is true, increment offset by limit to fetch the next page. Use after/before (ISO 8601) to filter by received date. For full email content, use get_email. Requires Outlook to be running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoOnly include emails received on or after this ISO 8601 date (e.g., "2025-01-01T00:00:00Z"). If omitted, no start date filter.
limitNoMaximum number of emails to return, 1-100 (e.g., 10). Defaults to 25 if omitted.
beforeNoOnly include emails received on or before this ISO 8601 date (e.g., "2025-12-31T23:59:59Z"). If omitted, no end date filter.
offsetNoNumber of emails to skip for pagination (e.g., 25 for page 2). Defaults to 0 if omitted.
folder_idYesThe folder ID to list emails from (e.g., from list_folders)
unread_onlyNoIf true, only return unread emails. Defaults to false if omitted.
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It explains ordering, body preview, return shape, pagination, date filtering, and the prerequisite that Outlook must be running. It does not mention all potential edge cases but covers key behaviors well.

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 concise and front-loaded with the main purpose, then progresses to details like preview size, return structure, pagination, and alternatives. Every sentence adds value without redundancy.

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?

Given the 6-parameter schema and no output schema or annotations, the description covers the essential aspects: purpose, ordering, preview, return shape, pagination, filtering, and environment requirement. It could elaborate on the structure of individual items but the provided information is sufficient for an agent to invoke it correctly.

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?

The input schema already provides 100% coverage with descriptions, so baseline is 3. The description adds usage semantics by explaining how to paginate with offset/limit and how to use after/before together, going beyond the schema's individual parameter descriptions.

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 tool lists email summaries in a specific folder, ordered newest first. It distinguishes from siblings by specifying the summary format and pagination behavior, and also references get_email for full content.

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?

The description provides clear context for when to use this tool (browsing summaries by folder) and explicitly names get_email as the alternative for full email content. It does not explicitly contrast with search_emails, but the folder-scoped use case is evident.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hasan-imam/mcp-outlook-applescript'

If you have feedback or need assistance with the MCP directory API, please join our Discord server