Skip to main content
Glama

graph_list_worksheets

List the worksheets in an Excel workbook through Microsoft Graph, with paging support for large workbooks. Use it to discover sheet names and IDs before reading or writing cells.

Instructions

List the worksheets in an Excel workbook.

Excel workbook APIs need the Files.ReadWrite permission and only work on .xlsx files.

Args: item_id: The workbook file ID. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list). drive_id: Drive ID to act on. Empty targets your own OneDrive.

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": {
      "item_id": "<item_id>"
    },
    "name": "graph_list_worksheets"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
drive_idNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the permission requirement, the .xlsx-only restriction, and the paging contract, including that next_link overrides the other paging arguments. It does not say what happens on invalid item_id, non-workbook files, or whether hidden/veryHidden sheets are included.

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?

Purpose and constraints are front-loaded in two lines, then parameters are enumerated in a clean Args block. Slightly verbose in re-stating parameter names, but no sentence is filler and the pagination caveat is placed where it matters.

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?

There is no output schema, so the description must cover return shape — and it does, distinguishing a bare list from the {items, next_link} wrapper. Combined with the auth and file-type notes, an agent has enough to call this correctly; only error behavior remains undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the Args block documents all four parameters meaningfully. It explains that next_link is an opaque URL that overrides other paging args, that include_next_link changes the return shape to {items, next_link} versus a bare list, and that an empty drive_id targets the caller's own OneDrive — semantics the bare schema cannot convey.

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 opens with a specific verb and resource: 'List the worksheets in an Excel workbook.' That is unambiguous and clearly separable from other list tools such as graph_list_files or graph_list_drives. It stops short of naming a sibling or boundary case, so it is clear but not explicitly differentiated.

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?

It supplies real preconditions: the API needs Files.ReadWrite permission and only works on .xlsx files, which prevents an agent from attempting it on other file types or under-read-only auth. There is no explicit when-to-use-this-vs-alternative guidance (e.g., versus graph_list_files to discover the workbook), so it falls short of a 5.

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