Skip to main content
Glama
JonEricDelaCruz

onenote-mcp

by JonEricDelaCruz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Delete page

deletePage
Destructive

Permanently remove a OneNote page from your notebook. Requires confirmation of the exact page title to prevent accidental deletion.

Instructions

Permanently delete a page. This cannot be undone -- confirm the page title with the user before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesPage TITLE (e.g. "AI Search") or ID. Titles are matched case-insensitively; if several pages share one you get the list back to choose from. You do NOT need to look up an ID first.
confirmTitleYesThe exact current title of the page, as a safeguard. The call fails if it does not match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.1
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page TITLE (e.g. \"AI Search\") or ID. Titles are matched case-insensitively; if several pages share one you get the list back to choose from. You do NOT need to look up an ID first.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / pageId
      Removed value: -{
-  "description": "Page ID from listPages or searchPages.",
-  "minLength": 1,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "pageId",
-  "confirmTitle"
-]New value: +[
+  "page",
+  "confirmTitle"
+]
  2. First observedv2.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description adds critical context: the operation is irreversible ('cannot be undone') and requires user confirmation. This goes beyond what annotations alone convey and directly informs the agent of the irreversible consequence and the necessary pre-call action.

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?

The description is two concise sentences with no filler. The core action is front-loaded ('Permanently delete a page'), followed by the critical warning and usage instruction. Every sentence earns its place.

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

Completeness5/5

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

Given the tool's simplicity (2 required params, no output schema), the description plus schema fully cover what an agent needs: the action, the irreversibility, the confirmation step, and parameter semantics. Nothing essential is missing.

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 description coverage is 100%, with both page and confirmTitle thoroughly explained including matching rules and fallback behavior. The description only references the confirmation requirement without adding parameter details, so it correctly relies on the schema. Baseline 3 applies.

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 states a clear verb ('delete') and resource ('page') with an explicit qualifier ('permanently'), distinguishing it from mutation siblings like createPage or appendToPage. The action is unambiguous and immediately conveys the tool's destructive nature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The instruction to 'confirm the page title with the user before calling' provides a clear prerequisite for invocation. While it does not name alternative tools or explicitly state when not to use it, the context is obvious and the guideline is actionable. This is clear context with no exclusions, not explicit when/when-not guidance.

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