Skip to main content
Glama

delete-onenote-page

Destructive

Permanently remove a OneNote page by specifying its ID. Deletion is immediate and irreversible.

Instructions

Delete a OneNote page.

💡 TIP: Deletes a OneNote page permanently. This cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
If-MatchNoETag
onenotePageIdYesPath parameter: onenotePageId
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
Behavior4/5

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

Annotations already mark destructiveHint as true, but the description adds context by stating 'Deletes a OneNote page permanently. This cannot be undone.' This explains the irreversibility beyond the annotation. However, openWorldHint: true suggests potential side effects not elaborated.

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 very concise, front-loaded with the core action, and includes a helpful tip in a separate line. Every sentence adds value with no redundancy.

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?

Given 4 parameters, no output schema, and annotations present, the description covers the essential irreversibility but lacks details on concurrency handling (ETag), response options, and potential side effects hinted by openWorldHint. It is adequate but not thorough.

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 100%, so the baseline is 3. The description does not add any parameter-specific information (e.g., the role of 'If-Match' for concurrency control). It merely repeats the schema's purpose.

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 clearly states 'Delete a OneNote page,' specifying the verb 'delete' and the resource 'OneNote page.' This distinguishes it from sibling delete tools for other resources. However, it could be more explicit about the scope (e.g., page content only) to achieve 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives (e.g., moving to recycle bin, or using other delete tools). The tip about permanence implies careful use but lacks explicit when-not-to-use instructions or prerequisites.

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