Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

drive.files.emptyTrash

Permanently deletes all files in the user's trash to free up storage. Use it to clear trashed items irreversibly, optionally for a specific shared drive.

Instructions

Permanently deletes all of the user's trashed files. For more information, see Trash or delete files and folders [HTTP DELETE] — removes the resource; irreversible unless the API documents a trash/undo flow; refused under --readonly safety profiles. Returns the post-delete resource state (or empty) as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: copy, create, delete, download, export, generateCseToken, generateIds, get, list, listLabels, modifyLabels, update, watch.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
driveIdNo[query parameter] If set, empties the trash of the provided shared drive.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.
enforceSingleParentNo[query parameter] Deprecated: If an item isn't in a shared drive and its last parent is deleted but the item itself isn't, the item will be placed under its owner's root.false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / driveId / description
      Previous value: -"If set, empties the trash of the provided shared drive."New value: +"[query parameter] If set, empties the trash of the provided shared drive."
    • addedInput schema / properties / enforceSingleParent / default
      Added value: +"false"
    • changedInput schema / properties / enforceSingleParent / description
      Previous value: -"Deprecated: If an item isn't in a shared drive and its last parent is deleted but the item itself isn't, the item will be placed under its owner's root."New value: +"[query parameter] Deprecated: If an item isn't in a shared drive and its last parent is deleted but the item itself isn't, the item will be placed under its owner's root."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well: it flags HTTP DELETE, states the action is irreversible with no documented undo, notes it is refused under --readonly safety profiles, and describes the return value. Missing are permission requirements and a caution that this wipes the entire trash in one call.

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?

The irreversible, whole-trash deletion is front-loaded in the first sentence, and the destructive/return-body boilerplate is compressed into single clauses. Nothing here is repeated from the schema or wasted.

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 destructive, zero-parameter-required tool with no annotations and no output schema, the definition covers danger level, undoability, safety-profile refusal, and return shape. The one real gap is scope: it never says whether the shared-drive trash is included only when driveId is set, which matters greatly for an irreversible 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 coverage is 100%, so the fields — including driveId and dry_run — are already documented in the schema; the description adds only the precedence rule that typed flags win over the `params` map and that `body_file` replaces built bodies. That is useful mechanism context but no new meaning for the operationally important parameters.

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?

The opening sentence names a specific verb and resource with explicit scope: 'Permanently deletes all of the user's trashed files.' The word 'all' plus 'permanently' distinguishes it in spirit from drive.files.delete (single file), though the sibling list is dumped flat rather than used to draw that contrast.

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?

Usage is only implied by the verb and the sibling list. The description never says when to prefer this over drive.files.delete or a per-file removal, nor does it call out the shared-drive case that the driveId parameter enables. An agent must infer the choice from the word 'all'.

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