Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

drive_files_delete

DestructiveIdempotent

Permanently deletes a Google Drive file by file ID, removing it from storage when the file is no longer needed.

Instructions

Permanently delete a file.

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": "drive_files_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesThe file ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely carried by structured data. The description adds one genuinely useful fact beyond that: deletion is permanent, i.e. not recoverable via trash. It says nothing about required permissions, ownership, or what happens to a file already deleted.

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?

Four words, front-loaded, zero filler. It is efficient but borders on under-specification rather than excess, which is captured elsewhere.

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 single-parameter destructive tool with full schema coverage and rich annotations and no output schema, the definition is minimally sufficient. It omits permission prerequisites and any failure behavior (file not found, insufficient access), which an agent calling a permanent-delete endpoint would benefit from knowing.

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?

One parameter with 100% schema description coverage ("The file ID to delete"), so the schema already does the explanatory work. The description adds no format hints, no mention that the ID must be a Drive file ID rather than a path or name, so baseline 3 applies.

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 and resource ("delete a file") and adds the qualifier "Permanently," which distinguishes this from a soft-delete/trash operation. It is not explicit about how it differs from the other delete siblings (comments, permissions, replies), but the name plus description leave no real ambiguity about what is removed.

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 or when-not-to-use guidance, no stated prerequisites, and no pointer to alternatives such as drive_files_update for renaming or a trash/restore path. The agent must infer that this is the terminal removal step.

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