Skip to main content
Glama
collero
by collero

Onenote Update Page

onenote_update_page

Appends plain-text content to an existing OneNote page without altering its original formatting; optionally guards against overwriting concurrent edits using a last-modified timestamp.

Instructions

APPEND bodyText as one new plain-text paragraph at the end of the OneNote page identified by pageId. Never replaces or reformats existing content — the page's original formatting (bullets, tables, images) is preserved untouched, so updating a formatted page is safe.

dateExpectedLastModified is a conflict guard, not a write-back of the read body: pass lastModifiedDateTime exactly as onenote_get_page returned it, and a mismatch (the page changed since your read) raises [onenote_page_conflict] — re-read and retry with the fresh value. OMIT the field for an UNGUARDED overwrite (no concurrency check at all): the escape hatch for a page that keeps rejecting a freshly-read value, which OneNote's lazily-stamped timestamps can cause on pages not written recently. The page's owning notebook is checked against the writable-notebook allowlist before any write, same as onenote_create_page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdYes
bodyTextYes
dateExpectedLastModifiedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
page_idYes
body_textYes
section_idNo
notebook_idNo
section_nameYes
last_modifiedNo
notebook_nameYes
body_text_incompleteNo
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It explains the append-only guarantee, preservation of original formatting, the conflict guard mechanism, the exact error raised on mismatch, the unguarded overwrite escape hatch, and the notebook allowlist check. This is exceptional transparency.

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 longer than average, but every sentence adds essential operational detail. It front-loads the core behavior first, then explains the conflict guard, then the allowlist context. There is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, three parameters, and complete absence of annotations or schema descriptions, the description covers everything an agent needs: what the tool does, how each parameter behaves, failure modes, retry guidance, and permissions context. The output schema exists, so not detailing return values is acceptable.

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 description coverage is 0%, so the description must explain the parameters, and it does. bodyText is defined as a plain-text paragraph, pageId is the page target, and dateExpectedLastModified gets a detailed explanation of its role as a conflict guard, including how to obtain it, when to omit it, and what happens on mismatch.

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 opens with a specific verb and resource: 'APPEND bodyText as one new plain-text paragraph at the end of the OneNote page.' It also explicitly distinguishes the behavior from replacing or reformatting content, which separates it from related page tools like onenote_create_page.

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 gives clear practical context: when to use, how to handle conflict-guard values, and when to omit the guard for an unguarded overwrite. It references onenote_get_page and onenote_create_page for related behavior, but it does not explicitly state exclusions such as 'create a new page instead' or 'use search instead.'

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/collero/winMCP'

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