Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

update_draft

Partially update a saved Outlook draft by supplying only the fields to change; omitted fields stay as-is. Use it to revise recipients, subject, or body before sending.

Instructions

Partially update a saved Draft. Only fields you supply are changed — omitted fields are left as-is on the server. Use list_messages(folder: 'drafts') to find Draft IDs.

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": {
      "messageId": "<messageId>"
    },
    "name": "update_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoReplace CC recipients
toNoReplace To recipients
bccNoReplace BCC recipients
bodyNoNew body content
subjectNoNew subject line
messageIdYesThe Draft message ID to update
contentTypeNoBody content type (only used when body is supplied, default: 'text')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 burden, and it does disclose the most important trait: omitted fields are left as-is on the server, distinguishing this from a full replace. It says nothing about permission/auth requirements, whether the draft remains a draft afterward, whether contentType changes rewrite the body, or what the call returns.

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 operation and its partial-update rule, followed by the prerequisite hint. No filler, no repetition of the title, and every sentence carries distinct information.

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 7-parameter mutation tool with no annotations and no output schema, the definition covers the essentials: what it mutates, how omission behaves, and how to obtain the required ID. The remaining gaps — auth/permission expectations and the effect on draft state — are modest but real.

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 each parameter is already documented, and the enum on contentType is self-explanatory — baseline 3 applies. The sentence about omitted fields being unchanged adds genuine semantics the schema's 'Replace ...' wording does not spell out, but there is no per-parameter elaboration beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource — 'Partially update a saved Draft' — which immediately signals PATCH-style semantics rather than create or send, separating it from siblings like save_draft or send_draft. It stops short of explicitly naming those alternatives, so the differentiation is implied by the verb rather than stated.

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?

Gives an actionable prerequisite path: 'Use list_messages(folder: 'drafts') to find Draft IDs', which resolves the one required parameter. It does not state when not to use it (e.g., to create a new draft use save_draft, or to dispatch it use send_draft), so the alternative-selection guidance is incomplete.

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