Microsoft 365 MCP Server

create-onenote-section

create-onenote-section

Destructive

Create a new OneNote section in a specified notebook by providing the section name. Use this to organize notebook content into separate sections.

Instructions

Create a new onenoteSection in the specified notebook.

💡 TIP: Creates a new section in a notebook. Body: { displayName: 'Section Name' }.

Input Schema

Name	Required	Description
`body`	Yes
`confirm`	No	For 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.
`notebookId`	Yes	Value for the 'notebookId' path segment. Pass it under the name 'notebookId', not as 'id'. Use the 'id' field of the notebook object as returned by Microsoft Graph.
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`excludeResponse`	No	Exclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedv0.176.1Oct 29, 2026

addedInput schema / $defs / def10
```
Added value: +{
+  "type": "boolean"
+}
```

removedInput schema / $defs / def4 / properties / createdDateTime / description

Removed value: -"The date and time when the page was created. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

removedInput schema / $defs / def4 / properties / lastModifiedDateTime / description

Removed value: -"The date and time when the page was last modified. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

removedInput schema / $defs / def4 / properties / level / description
```
Removed value: -"The indentation level of the page. Read-only."
```

removedInput schema / $defs / def4 / properties / order / description

Removed value: -"The order of the page within its parent section. Read-only."

removedInput schema / $defs / def5 / properties / createdDateTime / description

Removed value: -"The date and time when the page was created. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

removedInput schema / $defs / def5 / properties / lastModifiedDateTime / description

Removed value: -"The date and time when the notebook was last modified. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

removedInput schema / $defs / def6 / properties / createdDateTime / description

Removed value: -"The date and time when the page was created. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

removedInput schema / $defs / def6 / properties / lastModifiedDateTime / description

Removed value: -"The date and time when the notebook was last modified. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

removedInput schema / $defs / def7 / properties / createdDateTime / description

Removed value: -"The date and time when the page was created. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

removedInput schema / $defs / def7 / properties / lastModifiedDateTime / description

Removed value: -"The date and time when the notebook was last modified. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

addedInput schema / $defs / def8
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / $defs / def9
```
Added value: +{
+  "type": "boolean"
+}
```

removedInput schema / properties / body / properties / createdDateTime / description

Removed value: -"The date and time when the page was created. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

removedInput schema / properties / body / properties / lastModifiedDateTime / description

Removed value: -"The date and time when the notebook was last modified. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."

addedInput schema / properties / confirm / allOf

Added value: +[
+  {
+    "$ref": "#/$defs/def8"
+  }
+]

removedInput schema / properties / confirm / type
```
Removed value: -"boolean"
```

addedInput schema / properties / excludeResponse / allOf

Added value: +[
+  {
+    "$ref": "#/$defs/def9"
+  }
+]

removedInput schema / properties / excludeResponse / type
```
Removed value: -"boolean"
```

addedInput schema / properties / includeHeaders / allOf

Added value: +[
+  {
+    "$ref": "#/$defs/def10"
+  }
+]

removedInput schema / properties / includeHeaders / type
```
Removed value: -"boolean"
```

Addedv0.134.4Jul 28, 2026
Removedv0.131.2Jul 18, 2026

Changed7 schema fields changedv0.131.2Jul 18, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
removedInput schema / properties / body / properties / pages / items / properties / parentNotebook / properties / sectionGroups / items / properties / sections / items / $ref
```
Removed value: -"#/properties/body"
```
addedInput schema / properties / body / properties / pages / items / properties / parentNotebook / properties / sectionGroups / items / properties / sections / items / additionalProperties
```
Added value: +true
```

added

Input schema / properties / body / properties / pages / items / properties / parentNotebook / properties / sectionGroups / items / properties / sections / items / properties

Added value: +{
+  "createdBy": {
+    "$ref": "#/properties/body/properties/createdBy"
+  },
+  "createdDateTime": {
+    "anyOf": [
+      {
+        "description": "The date and time when the page was created. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only.",
+        "format": "date-time",
+        "pattern": "^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "The date and time when the page was created. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."
+  },
+  "displayName": {
+    "description": "The name of the notebook.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "id": {
+    "description": "The unique identifier for an entity. Read-only.",
+    "type": "string"
+  },
+  "isDefault": {
+    "description": "Indicates whether this is the user's default section. Read-only.",
+    "type": [
+      "boolean",
+      "null"
+    ]
+  },
+  "lastModifiedBy": {
+    "$ref": "#/properties/body/properties/createdBy"
+  },
+  "lastModifiedDateTime": {
+    "anyOf": [
+      {
+        "description": "The date and time when the notebook was last modified. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only.",
+        "format": "date-time",
+        "pattern": "^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "The date and time when the notebook was last modified. The timestamp represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. Read-only."
+  },
+  "links": {
+    "$ref": "#/properties/body/properties/links"
+  },
+  "pages": {
+    "description": "The collection of pages in the section.  Read-only. Nullable.",
+    "items": {
+      "$ref": "#/properties/body/properties/pages/items"
+    },
+    "type": "array"
+  },
+  "pagesUrl": {
+    "description": "The pages endpoint where you can get details for all the pages in the section. Read-only.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "parentNotebook": {
+    "$ref": "#/properties/body/properties/pages/items/properties/parentNotebook"
+  },
+  "parentSectionGroup": {
+    "$ref": "#/properties/body/properties/pages/items/properties/parentNotebook/properties/sectionGroups/items"
+  },
+  "self": {
+    "description": "The endpoint where you can get details about the page. Read-only.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedInput schema / properties / body / properties / pages / items / properties / parentNotebook / properties / sectionGroups / items / properties / sections / items / type
```
Added value: +"object"
```

changed

Input schema / properties / body / properties / pages / items / properties / parentNotebook / properties / sections / items / $ref

Previous value: -"#/properties/body"New value: +"#/properties/body/properties/pages/items/properties/parentNotebook/properties/sectionGroups/items/properties/sections/items"

changedInput schema / properties / body / properties / pages / items / properties / parentSection / $ref

Previous value: -"#/properties/body"New value: +"#/properties/body/properties/pages/items/properties/parentNotebook/properties/sectionGroups/items/properties/sections/items"

Changed1 schema field changedv0.131.1Jul 11, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "For 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.",
+  "type": "boolean"
+}

Addedv0.114.0May 28, 2026
Removedv0.112.2May 22, 2026
Addedv0.110.0May 18, 2026
Removedv0.108.0May 15, 2026
Addedv0.96.0May 4, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, and the description adds nothing beyond restating that a section is created. It does not mention the confirmation gate, permission requirements, or that the operation is irreversible, all of which matter for a tool flagged destructive.

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?

Two short, front-loaded sentences with the action stated first and the body shape second; nothing is padded. The TIP sentence partly restates the first sentence, which is minor redundancy but still earns its place by giving the payload shape.

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?

Annotations and a rich schema cover the safety profile and parameters, and no output schema means return values need no explanation. For a destructive create operation, though, the description omits confirmation-gate behavior, prerequisites, and error conditions that an agent would need to call it safely.

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 coverage is 80%, so the baseline is 3, and the tip 'Body: { displayName: \'Section Name\' }' genuinely helps because the body schema is a sprawling Graph object full of read-only fields. However, the description says nothing about notebookId, confirm, or excludeResponse, so it does not fully compensate for the remaining coverage gap.

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?

States a specific verb and resource ('Create a new onenoteSection') plus the parent scope ('in the specified notebook'), which separates it from create-onenote-notebook and create-onenote-section-page. It stops short of naming those siblings or stating the containment relationship explicitly, so an agent must infer the hierarchy.

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?

The phrase 'in the specified notebook' implies a notebook must already exist and be identified, which is the only usage signal given. There is no guidance on how to obtain the notebookId (e.g., via list-onenote-notebooks) and no when-not-to-use or alternative tool named.

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

Deploy Server

create-onenote-section

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools