Skip to main content
Glama
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria

update-onenote-page-content

update-onenote-page-content
Destructive

Edit OneNote page content by appending, inserting, replacing, or deleting HTML elements at specified targets, allowing precise updates to pages via the Microsoft 365 MCP Server.

Instructions

Update OneNote page content.

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": {
      "body": "<body>",
      "onenotePageId": "<onenotePageId>"
    },
    "name": "update-onenote-page-content"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
confirmNoFor destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: "confirmation_required" } without touching user data.
onenotePageIdYesValue for the 'onenotePageId' path segment. Pass it under the name 'onenotePageId', not as 'id'. Use the 'id' field of the onenote page object as returned by Microsoft Graph.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.184.0
    • changedInput schema / properties / body / items / properties / target / description
      Previous value: -"Element to change: a data-id, the generated id, or a known name like 'body' or 'title'."New value: +"Element to change: #<data-id>, a generated id (no #), or 'body' or 'title'. Most replace actions need the generated id: read the page content with includeIDs=true, and again after each update, as ids can change."
  2. Addedv0.176.1

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety posture is known, but the description adds nothing beyond them. It does not note that the body is an array of operations applied together, that some actions destroy existing content, or that read-back after each update may be needed — the only such hints live inside parameter descriptions, not the tool description.

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

Conciseness3/5

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

One short sentence with zero waste, so it is concise and front-loaded, but that brevity comes from under-specification rather than tight editing. There is no structure because there is no content to structure.

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?

For a destructive, batched page-mutation tool, the description omits what a caller most needs to know: that operations are applied as a batch, that content must be HTML, and that destructive actions can be gated. The rich input schema and annotations compensate partially, but the prose leaves a real gap.

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 80% and the parameter descriptions are unusually detailed (target id volatility, action enum semantics, the confirm gate behavior). The description itself contributes nothing to parameter meaning, so the baseline 3 applies.

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

Purpose2/5

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

"Update OneNote page content" restates the tool name and title almost verbatim, adding no scope detail. It never says that the update is a batch of HTML content operations (append/insert/prepend/replace/delete) against a specific page, which is what actually distinguishes this tool from create-onenote-page or get-onenote-page-content.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — no indication of when to update versus create/delete a page, no prerequisites such as needing page ids from get-onenote-page-content, and no mention of the confirm gate. An agent must infer everything from the schema and sibling names.

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