Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria

create-onenote-section

create-onenote-section
Destructive

Create a new section in a specified OneNote notebook to organize pages. Provide the notebook ID and a display name to add a section.

Instructions

Create a new onenoteSection in the specified notebook.

šŸ’” TIP: Creates a new section in a notebook. Body: { displayName: 'Section Name' }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
confirmNoFor 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.
notebookIdYesValue 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.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.134.4
  2. Removedv0.131.2
  3. Changed7 schema fields changedv0.131.2
    • 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
    • addedInput 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"
    • changedInput 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"
  4. Changed1 schema field changedv0.131.1
    • 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"
      +}
  5. Addedv0.114.0
  6. Removedv0.112.2
  7. Addedv0.110.0
  8. Removedv0.108.0
  9. Addedv0.96.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint: true and readOnlyHint: false. The description adds a payload example but does not elaborate on side effects, permissions, or the actual creation process. No contradiction with annotations.

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 brief (one sentence plus a tip) and front-loaded. No extraneous text, though the tip could be integrated more concisely.

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?

The tool has 5 parameters, no output schema, and nested objects. The description covers the basic purpose but omits details about return values, error scenarios, or required permissions. Adequate but not comprehensive.

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 high (80%), and the description adds value by showing an example body structure with 'displayName'. This clarifies the expected content beyond the schema's property 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 the verb 'Create' and the resource 'onenoteSection', specifying 'in the specified notebook'. It distinguishes from sibling tools like 'create-onenote-notebook' and 'create-onenote-section-page' through the target resource.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., when to use a section group). The tip provides an example body but does not clarify context or exclusions.

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/Softeria/ms-365-mcp-server'

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