gsuite

google-drive_delete_file

Permanently delete a file from Google Drive by specifying its file ID. Optionally include support for shared drives.

Instructions

Permanently delete a file. Returns 204 No Content with empty body on success.

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": {
      "fileId": "<fileId>"
    },
    "name": "google-drive_delete_file"
  }
}

Input Schema

Name	Required	Description	Default
`fileId`	Yes	ID of the file to delete
`supportsAllDrives`	No	Whether to support files in shared drives

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Jul 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Without annotations, the description carries the burden. It discloses permanence, which is critical for a delete operation. However, it omits other behavioral traits like permission requirements or effects on shared drives (only hinted via the supportsAllDrives parameter in schema).

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 sentences, concise and to the point. No wasted words; every sentence adds value.

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 simple delete operation with two parameters and no output schema, the description covers the action and response. It could note that deletion is irreversible and might require permissions, but it's largely complete.

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 100% (both fileId and supportsAllDrives are described in the schema). The description adds no extra meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 clearly states that the tool permanently deletes a file and indicates the HTTP response (204 No Content). This distinguishes it from sibling tools like google-drive_update_file or google-drive_share_file, which have different actions.

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 guidance on when to use this tool versus alternatives, such as trashing via update or requiring owner permissions. The description implies usage for deletion but provides no exclusions or prerequisites.

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