Skip to main content
Glama
umangnine

OneNote MCP Server

by umangnine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_page

Create a new page in a OneNote notebook section using HTML rich text, with support for headings, lists, links, tables, and basic formatting.

Instructions

Create a new page in a OneNote notebook section.

The content is written as HTML with full rich-text support.
Supported tags: h1-h6 (headings with auto font sizing), p, ul/ol/li (lists
with bullets/numbers), b/strong (bold), i/em (italic), u (underline),
span (with style), a (links), hr (horizontal rule), br, table/tr/td/th.

Headings get automatic font sizes: h1=24pt, h2=18pt, h3=14pt, h4=13pt,
h5=12pt, h6=11pt. All body text is 11pt minimum.

Requires the OneNote desktop app to be installed.

Args:
    notebook_name: Name of the notebook (from list_live_notebooks).
    section_name: Name of the section within the notebook.
    title: Title for the new page.
    content: The page content as HTML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
contentYes
section_nameYes
notebook_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 one meaningful environmental trait: the OneNote desktop app is required. However, it says nothing about failure modes (missing section/notebook), permissions, or whether a duplicate title is allowed, leaving key behavioral questions unanswered.

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?

Purpose is front-loaded in sentence one, followed by format documentation and prerequisites, with the Args block last. The tag list and font-size table are verbose but earn their place by defining valid content input; nothing is duplicated fluff.

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?

An output schema exists, so return values need no explanation, and the description covers the input contract plus the desktop-app prerequisite. For a no-annotation creation tool it is nearly complete, missing only error/duplicate handling behavior.

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

Parameters4/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 does: the Args block documents all four parameters, notes that notebook_name comes from list_live_notebooks, and defines content as HTML. section_name and title get only bare restatements, so it is strong but not exhaustive.

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?

The first sentence states a specific verb and resource ('Create a new page in a OneNote notebook section'), and 'new page' naturally contrasts with siblings like append_to_page and update_page_content. It is clear without opening the schema, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: creating a new page versus appending to or updating one is left for the agent to infer from sibling names. The only routing hint is that notebook_name comes 'from list_live_notebooks', which is a parameter-sourcing note, not a when-to-use rule.

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