Skip to main content
Glama

graph_delete_file

Delete a OneDrive file or folder by item ID, moving it to the recycle bin for later recovery.

Instructions

Delete a file or folder from OneDrive.

The item is moved to the OneDrive recycle bin.

Args: item_id: The file or folder ID to delete.

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_delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key trait for a destructive operation — the item goes to the recycle bin rather than being permanently erased — but says nothing about required permissions, whether deleting a folder deletes its contents, or how failures surface.

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?

Two short sentences plus an Args block; the most important fact (delete) is front-loaded and the recycle-bin consequence follows immediately. The Args block only restates the single parameter name, which is mild redundancy but not harmful.

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 one-parameter, non-annotated mutation tool with no output schema, the definition covers what is deleted and where it goes. It omits permission requirements and recursive-folder semantics, which matter for correct invocation of a destructive call.

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 0%, so the description must compensate for a single required parameter. It clarifies that item_id may identify either a file or a folder, which adds real meaning, but gives no hint about the expected ID format or where the agent obtains it.

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 (delete) and resource (a file or folder in OneDrive), which cleanly distinguishes it from the many other delete siblings scoped to permissions, messages, contacts, or events. It stops short of naming any sibling or contrasting behavior, so it earns a 4 rather than a 5.

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?

No when-to-use / when-not-to-use guidance and no prerequisites (ownership, required permissions, whether folder deletion is recursive). The recycle-bin note implies the action is recoverable but does not route the agent to any alternative for permanent removal or restoration.

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