Skip to main content
Glama
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria

get-onenote-page-content

get-onenote-page-content
Read-only

Retrieve the HTML content of a OneNote page by page ID, with options to include element IDs, response headers, or fetch up to 100 pages for full export.

Instructions

The page's HTML content.

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": {
      "onenotePageId": "<onenotePageId>"
    },
    "name": "get-onenote-page-content"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeIDsNoAdd each element's generated id, for use as an update target.
fetchAllPagesNoFollow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search.
onenotePageIdYesValue for the 'onenotePageId' path segment. Pass it under the name 'onenotePageId', not as 'id'. Use the 'id' field of the onenote page 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.

  1. Changed1 schema field changedv0.184.0
    • addedInput schema / properties / includeIDs
      Added value: +{
      +  "description": "Add each element's generated id, for use as an update target.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv0.134.4
    • changedInput schema / properties / onenotePageId / description
      Previous value: -"Path parameter: onenotePageId"New value: +"Value for the 'onenotePageId' path segment. Pass it under the name 'onenotePageId', not as 'id'. Use the 'id' field of the onenote page object as returned by Microsoft Graph."
  3. Addedv0.131.2
  4. Removedv0.131.2
  5. Addedv0.114.0
  6. Removedv0.112.2
  7. Addedv0.110.0
  8. Removedv0.108.0
  9. Changed1 schema field changedv0.96.0
    • changedInput schema / properties / fetchAllPages / description
      Previous value: -"Automatically fetch all pages of results"New value: +"Follow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search."
  10. First observedv0.31.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the description has a lower bar but still adds nothing. It does not mention that the response can be enormous, that pagination exists, or how the HTML relates to the includeIDs update-target feature documented only in the schema.

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

Conciseness3/5

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

It is a single short sentence with zero padding, so nothing is wasted, but it is so terse that it fails to front-load the retrieval verb or any risk. Brevity here reads as under-specification rather than efficiency.

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?

There is no output schema, so the description does carry the burden of telling the agent what comes back, and 'HTML content' does that minimally. However, for a 5-parameter tool whose schema warns about enormous payloads and pagination, the description leaves the agent without the context needed to call it safely.

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%, so every one of the five parameters is already documented, which sets the baseline at 3. The description adds no parameter meaning beyond the schema and does not reinforce which parameter drives pagination risk.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (the page) and the returned format (HTML content), but never states the verb explicitly, so retrieval is only implied by the tool name. It does not distinguish itself from siblings such as get-mail-attachment-content or get-excel-range that also fetch content.

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 like list-onenote-pages or get-download-url. The agent must infer that a page id is required and that this fetches rather than mutates.

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