Skip to main content
Glama

drive delete file

drive_delete_file
DestructiveIdempotent

Permanently delete a Google Drive file by setting confirm=true; this action is irreversible.

Instructions

Permanently delete a Drive file. Requires confirm=true; 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": {
      "file_id": "<file_id>"
    },
    "name": "drive_delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
file_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the destructive nature is not new information, but the description adds two things annotations cannot express: the deletion is irreversible and a confirm=true flag is mandatory. That prerequisite is critical because the schema defaults confirm to false, which would otherwise cause silent failures.

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 short sentences with zero filler. The destructive action is stated first and the precondition second, which is the right reading order for an agent deciding whether to call it.

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?

An output schema exists, so return values need no explanation, and the two-sentence description covers the essentials for a destructive two-parameter tool. It leaves out secondary context such as permission requirements or behavior on shared drives, but nothing that would cause an incorrect 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 carries the burden. It correctly explains the non-obvious parameter (confirm must be true, not the default false), which is genuinely useful, but adds nothing about file_id beyond its title. Partial compensation for the coverage gap lands this at adequate rather than strong.

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?

"Permanently delete a Drive file" gives a specific verb (delete) plus resource (Drive file) and the qualifier "permanently" separates it from soft-delete behavior. It stops short of naming drive_trash_file as the reversible alternative, so the sibling distinction is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "permanently" hints that a reversible alternative exists, but the description never says when to use this versus drive_trash_file or drive_move_file. An agent must infer the routing decision from the adjective alone.

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