Skip to main content
Glama

graph_delete_file_permission

Revoke a sharing link or a person's access to a file or folder by removing an existing permission, so sensitive content is no longer shared.

Instructions

Revoke a sharing link or a person's access to a file or folder.

Args: item_id: The file or folder ID. permission_id: The permission ID (from graph_list_file_permissions). 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>",
      "permission_id": "<permission_id>"
    },
    "name": "graph_delete_file_permission"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
drive_idNo
permission_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It identifies the mutation and target, but does not disclose required permissions, whether revocation is reversible, side effects, or error behavior. This leaves important operational behavior undocumented for a destructive action.

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

Conciseness5/5

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

The description is front-loaded, concise, and structured with a clear Args section. Every line contributes useful information without unnecessary wording.

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?

For a simple three-parameter operation it gives enough to invoke the tool correctly, including parameter meanings. However, with no annotations and no output schema, it should say more about permission prerequisites and the irreversible consequences of revoking access.

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%, so the description must compensate, and it does: all three parameters are explained. It clarifies permission_id provenance and the special drive_id default behavior when left empty.

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

Purpose5/5

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

The description uses a specific verb, 'Revoke', and clearly states the resource: a sharing link or a person's access to a file or folder. It distinguishes the operation from deleting the file itself and references the sibling used to obtain the permission ID.

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?

The usage context is clear: revoke sharing access rather than delete a file. It also helpfully points to graph_list_file_permissions as the source of permission_id. However, it does not explicitly state when not to use this tool or name alternatives.

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