Microsoft Graph MCP Server

create_page

Create a OneNote page in a specified section using HTML content and an optional title. Add structured notes or documents directly to your Microsoft 365 OneNote notebook.

Instructions

Create a OneNote page. html_content: HTML body 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": {
      "section_id": "<section_id>",
      "html_content": "<html_content>"
    },
    "name": "create_page"
  }
}

Input Schema

Name	Required	Description	Default
`title`	No
`section_id`	Yes
`html_content`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only states that a page is created and mentions html_content; it does not disclose output behavior, what happens with the optional title, required section_id semantics, or any side effects beyond 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 short and front-loaded, with no filler or repetition. The added parameter clarification earns its place, though the brevity comes at the cost of completeness.

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 create operation with no annotations, no output schema, and 3 parameters, the description lacks important context: what section_id refers to, whether title is required for the page, and what the result or return value is. The description is not complete enough for an agent to invoke the tool confidently without additional inference.

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

Parameters2/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 compensate for the missing parameter documentation. It only provides a gloss for html_content ('HTML body content') and leaves the required section_id and optional title unexplained. This is insufficient for fully understanding how to invoke the tool correctly.

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 a specific verb and resource: 'Create a OneNote page.' This is not a tautology and distinguishes the operation from update/delete/list page tools among the siblings. The resource type is specific enough to avoid confusion with other create_* tools.

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 guidance about when to use this tool versus alternatives, no mention of prerequisites, and no indication of how it relates to sibling tools like update_page_content or list_sections. The usage context is only implied by the name and the word 'create.'

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

Deploy Server