Skip to main content
Glama

Create OneNote Page

create_onenote_page

Create a OneNote page in a specified section from HTML; use it to add notes while accounting for OneNote's constrained HTML support, which drops unsupported CSS and tags.

Instructions

Create a OneNote page in a section. Content is HTML — OneNote supports a constrained subset and silently drops unsupported CSS/tags.

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>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_onenote_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesPage title
contentYesPage body as HTML (e.g. <p>Hello</p>)
section_idYesSection ID to create the page in

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations only say it is a non-read-only, non-destructive write. The description adds genuinely non-obvious behavior: only a constrained HTML subset is honored and unsupported CSS/tags are dropped silently, which warns the agent that content can be lost without error. It does not cover permissions, preconditions (section must already exist), or limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences: the action and target come first, followed by the single most important caveat. No filler and nothing buried.

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?

With three required parameters and no output schema, the definition should say what comes back (page ID, URL) so the agent can chain into get_onenote_page_content or update_onenote_page_content, and it does not. The silent-drop caveat is valuable, but preconditions and return value remain undocumented.

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 100%, so the baseline is 3, but the description adds real meaning about the 'content' parameter beyond the schema's brief '<p>Hello</p>' example by specifying a constrained HTML subset with silent dropping of unsupported markup. Title and section_id semantics are left entirely to the schema.

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 OneNote page') plus the parent container ('in a section'), so the agent knows exactly what is produced and where. It does not explicitly distinguish itself from siblings like copy_onenote_page or update_onenote_page_content, so it stops short of a 5.

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 by the verb 'create' plus the requirement to target a section, but there is no explicit when-to-use guidance and no mention of alternatives such as update_onenote_page_content for existing pages or copy_onenote_page for duplicating. The agent must infer the create-vs-update boundary.

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