Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_trash

Destructive

Move a file or folder to Google Drive trash, where it stays recoverable for 30 days, or restore a previously trashed item by its file ID.

Instructions

Move a file/folder to the Drive trash (recoverable for 30 days), or restore it.

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_trash"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYes
restoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new context beyond them: the deletion is recoverable for 30 days, which tells the agent the action is reversible within a window. It stops short of stating permission requirements or what happens after 30 days.

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?

A single sentence with no filler, leading with the primary action and parenthetically adding the recovery window before mentioning the reverse operation. Every clause carries information.

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 two-parameter tool with no output schema and annotations covering the safety profile, the description supplies the essential operational fact (30-day recoverability). It is nearly complete, missing only explicit mapping of the restore flag and any permission or error context.

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 must carry parameter meaning, and it only partly does. The file/folder target is clear, but the restore boolean is never named, never tied to its default of false, and no format guidance is given for fileId.

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 names a specific verb and resource ("Move a file/folder to the Drive trash") and covers the inverse operation ("or restore it") in the same sentence. An agent can distinguish this from siblings like drive_move or drive_get_file without opening any schema.

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 implied rather than stated: trashing versus restoring is described, but the description never says the restore parameter must be set, nor does it mention prerequisites such as the file already being in the trash. No alternatives or exclusions are named, so guidance is only inferable from the phrasing.

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