Skip to main content
Glama

list-onenote-section-pages

list-onenote-section-pages
Read-only

Retrieve page objects from a OneNote section by its ID. Supports filtering, searching, sorting, and pagination to get the exact pages needed.

Instructions

Retrieve a list of page objects from the specified section.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoPage size (Graph $top). Start small (e.g. 5–15) so responses fit the model context; raise only if needed. Use $select to return fewer fields per item. For more rows, use @odata.nextLink from the response instead of a very large $top.
skipNoItems to skip for pagination. Not supported with $search.
countNoSet true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains().
expandNoNavigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as a message body fails with "Parsing OData Select and Expand failed", and an unsupported value may be ignored rather than reported. Request ordinary fields with $select instead.
filterNoOData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search.
searchNoKQL search query — wrap value in double quotes. Cannot combine with $filter.
selectNoComma-separated fields to return, e.g. id,subject,from,receivedDateTime
orderbyNoSort expression, e.g. receivedDateTime desc
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.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
onenoteSectionIdYesValue for the 'onenoteSectionId' path segment. Pass it under the name 'onenoteSectionId', not as 'id'. Use the 'id' field of the onenote section object as returned by Microsoft Graph.
Behavior2/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, matching the read-only nature of 'retrieve'. However, the description adds no additional behavioral context beyond this. It does not mention pagination, response size, the need for selecting fields, or the possibility of large payloads. With annotations covering safety, the description is consistent but fails to add value like explaining that the tool follows OData conventions or that fetchAllPages can return huge results. It does not contradict annotations, but it is minimal.

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

Conciseness4/5

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

The description is a single, efficient sentence that clearly states the core function. It is not overly verbose and is front-loaded with the action and resource. However, it omits any context that might be useful, but conciseness itself is not the issue. It earns its place, though it could slightly expand to mention the section scoping without losing efficiency.

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

Completeness2/5

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

Given that there is no output schema and the tool has 12 parameters, the description is incomplete. It does not explain what the returned page objects contain, how pagination works, or that the tool is limited to a single section. With many sibling tools, an agent cannot determine when to use this vs. list-onenote-pages. The openWorldHint suggests behavior may vary, but the description gives no additional context. The schema helps with parameters but not with overall tool behavior or usage context.

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%, meaning all 12 parameters have descriptions in the schema. The tool description itself adds no parameter-level meaning, but the schema carries the burden. Per the rubric, with high coverage, a baseline of 3 is appropriate. The description does not add clarity beyond what the schema already provides, so it does not exceed the baseline.

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 'Retrieve a list of page objects from the specified section' clearly specifies the action (retrieve) and the resource (page objects within a section). It distinguishes from the sibling 'list-onenote-pages' by scoping to a section, though it does not explicitly name alternatives or contrast with them. The verb and resource are specific, but differentiation relies on the word 'section' rather than an explicit mention of when to use this tool over others.

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. It does not mention that it is for listing pages within a specific section, that users should have a section ID, or that other tools like 'list-onenote-pages' exist for broader queries. The schema includes detailed parameter descriptions but does not address tool selection context. No when/when-not guidance is provided.

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/A-Impact-Pavel/ms365-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server