Skip to main content
Glama

Delete OneNote Page

delete_onenote_page
Destructive

Delete a specified OneNote page by page ID. Use this when you need to remove a page permanently, since the API deletion cannot be undone.

Instructions

Delete a OneNote page. This cannot be undone via the API.

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": {
      "page_id": "<page_id>"
    },
    "name": "delete_onenote_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesPage ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description's main added value is the irreversibility disclosure. The qualifier 'via the API' is genuinely useful because it hints that recovery may be possible through other means, information not present in the annotations.

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 with zero waste; the action is stated first and the consequence immediately after. Nothing is repeated or padded.

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

Completeness4/5

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

For a one-parameter destructive tool with clear annotations and no output schema, the description covers the essentials: what it deletes and that it is not reversible. It stops short of stating what is returned (e.g., empty response) or any permission requirements, but these are minor for this complexity level.

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?

There is a single parameter with 100% schema description coverage ('Page ID to delete'), so the schema carries the load. The description adds no format, source, or validation detail about page_id beyond what is already documented.

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?

The description uses a specific verb ('Delete') and resource ('OneNote page'), which is unambiguous against siblings like create_onenote_page or update_onenote_page_content. It does not explicitly name an alternative, but the distinct resource makes confusion unlikely.

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 on when to use this tool versus alternatives (e.g., deleting a section or notebook instead, or archiving), and no stated prerequisites such as required permissions. The only implicit signal is the irreversibility warning, which functions as a caution rather than usage 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