Skip to main content
Glama
mhzarem

OneNote MCP Server

by mhzarem
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

create_page

Create a new page in a OneNote notebook section using HTML content. Specify notebook, section, title, and content to add notes programmatically.

Instructions

Create a new page in a OneNote notebook section.

The content is written as HTML. You can use basic HTML tags like
<b>, <i>, <br>, <ul>, <li>, <h1>-<h6>, etc.

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 (plain text or HTML).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
contentYes
section_nameYes
notebook_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.6/5.0
Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It mentions HTML support and desktop app requirement but omits side effects, validation, error handling, or confirmation of successful creation.

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 description is efficiently front-loaded with purpose and usage notes, and the Args section is structured. Could be slightly tighter, but overall effective.

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

Completeness3/5

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

Given 4 required params, no annotations, and an output schema, the description covers parameters and content format but lacks return value explanation and error handling, making it adequate but not complete.

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 description coverage is 0%, but the description provides clear semantic meaning for all parameters: notebook_name from list_live_notebooks, section_name, title, content as HTML or plain text, significantly compensating for missing schema descriptions.

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 clearly states 'Create a new page in a OneNote notebook section,' with a specific verb and resource, and distinguishes from siblings like append_to_page and list_* tools by focusing on creation.

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?

Provides some usage hints (HTML content, desktop app requirement) but does not explicitly guide when to use this vs alternatives like append_to_page for existing pages.

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/mhzarem/onenote-mcp'

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