OneDrive MCP Server

delete_file

Delete a file or folder from OneDrive, permanently removing all its contents. Use with caution as this action cannot be undone.

Instructions

Elimina un archivo o carpeta (con todo su contenido si es carpeta). Operacion irreversible.

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": {
      "filePath": "<filePath>"
    },
    "name": "delete_file"
  }
}

Input Schema

Name	Required	Description	Default
`filePath`	Yes	Ruta con prefijo del archivo o carpeta a eliminar

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly warns that folder deletion removes all contents and that the operation is irreversible, which are critical behavioral traits. It could add more details like permission requirements, but for a simple delete tool this is sufficient.

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?

Two concise sentences, front-loaded with the action and immediate caveats. Every word earns its place, with no fluff or repetition.

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?

Given the simple nature of the tool (one parameter, no output schema), the description covers the essential context: what it deletes, the recursive behavior, and irreversibility. It is complete enough for an agent to use correctly, though it could mention path prefix semantics in more detail.

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 for filePath has 100% coverage, so the description adds little extra meaning about the parameter. The tool description mentions that it deletes files or folders, which aligns with the parameter description, but does not provide additional context beyond the schema.

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 ('Elimina') and resource ('archivo o carpeta'), clearly stating it deletes files or folders with all contents if a folder. This distinguishes it from sibling tools like read_file, write_file, or move_file, showing it is the delete operation.

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 description implies when to use it (for deleting files/folders) and highlights the irreversible nature, which serves as a caution. However, it does not explicitly mention alternatives or when not to use it, such as preferring move_file for reversible actions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server