Skip to main content
Glama

list-drive-item-permissions

list-drive-item-permissions
Read-only

List all permissions (sharing links, direct access, inherited) on a OneDrive or SharePoint file or folder.

Instructions

The set of permissions for the item. Read-only. Nullable.

đź’ˇ TIP: Lists all permissions (sharing links, direct access, inherited) on a file or folder. Each permission has roles, grantedTo (user), link (sharing URL), and inheritedFrom.

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
driveIdYesValue for the 'driveId' path segment. Pass it under the name 'driveId', not as 'id'. Use the 'id' field of the drive object as returned by Microsoft Graph.
orderbyNoSort expression, e.g. receivedDateTime desc
driveItemIdYesValue for the 'driveItemId' path segment. Pass it under the name 'driveItemId', not as 'id'. Use the 'id' field of the drive item object as returned by Microsoft Graph.
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
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description redundantly repeats 'Read-only' and 'Nullable,' adding no new safety information. It does add some context about the output structure (roles, grantedTo, link, inheritedFrom), which is useful but not extensive. It does not mention pagination, potential large result sets, or response format beyond the field names, so behavioral disclosure is only partial.

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?

The description is concise, consisting of a short lead sentence and a tip. The lead sentence is almost tautological with the title, and the tip is appended with a lightbulb emoji but lacks clear structure (no separation of usage, output, or limitations). It is efficient but under-specified, so it does not earn a higher score for clarity.

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 the tool has 13 parameters, two required, and no output schema, the description should provide more context about the return shape, pagination behavior, and typical usage. It mentions some fields but does not explain how to handle large permission lists or how the parameters relate to each other. The schema covers parameter semantics, but the description leaves gaps in usage guidance and output expectations, making it incomplete for an agent to confidently use the tool in all scenarios.

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?

The schema description coverage is 100%, so all 13 parameters are already documented in detail (e.g., $top, $skip, $filter). The tool description does not add any parameter-specific meaning beyond what the schema provides. According to the rubric, a baseline of 3 applies when the schema fully documents parameters, and the description adds no extra value here.

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 the tool lists permissions on a file or folder and mentions the types of permissions (sharing links, direct access, inherited). It identifies the resource (drive item) and the verb (list), which is sufficient to understand its purpose. However, it does not explicitly distinguish it from sibling tools like delete-drive-item-permission, though the naming and context make the distinction obvious for a listing operation.

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 deletion or creation of permissions, nor does it state any prerequisites or conditions for use. The only contextual hint is the tip, which explains what the tool returns but not when to choose it over other permission-related tools.

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