Skip to main content
Glama

graph_list_file_permissions

Lists users and groups with access to a specified file or folder, with pagination support for continued review.

Instructions

List who currently has access to a file or folder.

Args: item_id: The file or folder 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_file_permissions"
  }
}

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

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does real work: it discloses that an empty drive_id targets the caller's own OneDrive, that next_link overrides the other paging arguments, and that include_next_link changes the return shape to {items, next_link} versus a bare list. It does not state required scopes/permissions or what each permission entry contains, which keeps it from a 5.

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?

One front-loaded sentence establishes the operation, followed by a tight Args block where every line adds new information. Slightly verbose line wrapping and a redundant restatement of the default in two places are the only waste.

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 four-parameter tool with 0% schema coverage and no output schema, the description covers all parameters, the paging protocol, and the two possible return shapes, which is close to what an agent needs to call it correctly. What is missing is the auth/permission requirement and the shape of individual permission entries.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it documents all four parameters with defaults and precedence semantics (next_link overriding other paging args, include_next_link defaulting to false, empty drive_id meaning own OneDrive). The remaining gap is item_id, which gets only 'The file or folder ID' with no format or source guidance.

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?

States a specific verb and resource: 'List who currently has access to a file or folder.' An agent can immediately tell this is a permissions-read operation, distinct from siblings like graph_delete_file_permission or graph_invite_to_file, though the description never names those siblings to reinforce the boundary.

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 when-to-use guidance, no prerequisites, and no exclusion relative to related tools such as graph_invite_to_file, graph_share_file, or graph_delete_file_permission. The agent must infer that this is the inspection counterpart to those mutation tools from the name alone.

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