Skip to main content
Glama

graph_create_mail_draft

Create a Microsoft Outlook email draft without sending it, with recipients, subject, body, CC/BCC, importance, and reply-to settings for later review or sending.

Instructions

Create a draft email without sending it.

Use graph_add_mail_attachment to attach files to the draft and graph_send_mail_draft to send it.

Args: to: List of recipient email addresses. subject: Email subject. body: Email body content. When is_html is true, send explicit HTML; markdown is not converted. cc: Optional list of CC email addresses. bcc: Optional list of BCC email addresses. is_html: Whether the body is HTML content (default: True). Use false for plain text. importance: Message importance: "low", "normal", or "high" (default "normal"). reply_to: Optional list of addresses that replies should be sent to. mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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": {
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "graph_create_mail_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyYes
is_htmlNo
mailboxNo
subjectYes
reply_toNo
importanceNonormal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does add real behavior: the draft is not sent, HTML is used verbatim with no markdown conversion, and the mailbox parameter requires delegated Mail.*.Shared permissions. It omits where the draft is stored and what identifier is returned for the follow-up send/attach calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key behavior and the two follow-up tools are front-loaded in the opening lines, and the args block is justified by the zero schema coverage. The prose is slightly verbose in the is_html and mailbox entries but no line is filler.

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 nine-parameter mutation with no annotations and no output schema, the description covers purpose, workflow, permissions, and every argument. The remaining gap is return-value information (draft ID) that an agent needs to chain into graph_add_mail_attachment and graph_send_mail_draft.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it documents all nine parameters with meaning beyond bare types: is_html controls literal HTML vs plain text with no markdown conversion, importance enumerates low/normal/high, mailbox semantics (empty = own mailbox) plus the required permission, and reply_to is explained as the reply destination.

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 ('Create a draft email') and immediately adds the scoping constraint 'without sending it', which separates it from graph_send_mail and graph_send_mail_draft without needing their schemas.

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 the agent forward: use graph_add_mail_attachment to attach files and graph_send_mail_draft to send, which defines a clear workflow. It does not explicitly name the alternative for the immediate-send case (graph_send_mail), though 'without sending it' implies the distinction.

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