Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

save_draft

Save an Outlook email as a draft without sending it, so you can prepare messages with subject, body, recipients, and attachments, then add recipients later.

Instructions

Save an email as a draft in Microsoft Outlook without sending it. Recipients are optional — a Draft can be started with just a subject and body, with recipients added later via update_draft. Supports CC, BCC, plain text or HTML body, and file attachments (max 3 MB each).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "save_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCC email addresses
toNoRecipient email addresses (optional — a Draft can be saved without recipients, to be added later via update_draft)
bccNoBCC email addresses
bodyYesEmail body content (required)
subjectYesEmail subject (required)
attachmentsNoLocal file paths to attach (max 3 MB per file)
contentTypeNoBody content type: 'text' for plain text, 'html' for HTML (default: 'text')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and discloses key traits: it does not send, recipients are optional, attachments are capped at 3 MB each, and body can be plain text or HTML. It does not mention what is returned, such as a draft ID, or where the draft appears.

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 concise sentences with the core non-sending behavior front-loaded and supporting details following efficiently. There is no wasted wording.

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?

Adequate for a relatively simple save-draft operation with a fully described input schema. The main remaining gap is return-value behavior, which matters because no output schema is provided.

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 all seven parameters are already documented. The description reinforces optional recipients and the attachment size limit, but adds little syntax or format detail 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?

States a specific verb and resource: saving an email as a draft in Microsoft Outlook. The phrase "without sending it" clearly distinguishes this from send_email and send_draft.

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?

Explains a clear draft-first workflow and says recipients are optional and can be added later via update_draft. It does not explicitly route sending to send_email or send_draft, but the non-sending boundary is clear.

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