Skip to main content
Glama

drive trash file

drive_trash_file
DestructiveIdempotent

Move a Drive file to trash so it stays recoverable for 30 days. Use this destructive action to remove files while keeping a restore option.

Instructions

Move a Drive file to trash (recoverable for 30 days). Destructive.

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

Input Schema

NameRequiredDescriptionDefault
file_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/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 trailing "Destructive" adds nothing. However, the 30-day recoverability window is real behavioral context not present in any structured field, and much of the burden is lifted by the existing annotations and output schema.

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?

Two short sentences, front-loaded with the action and scoped by the retention note. The final "Destructive." duplicates the annotation and could be dropped, but nothing else is wasted.

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?

With an output schema present and a single obvious parameter, the description covers what is needed to call the tool, but it omits routing guidance against drive_delete_file for a destructive operation where that choice matters.

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?

Only one parameter (file_id) at 0% schema description coverage, but its meaning is self-evident from its name and the description's framing of operating on "a Drive file." No added syntax, format, or constraints are offered beyond that.

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+resource ("Move a Drive file to trash") and adds the key nuance that the action is recoverable, which distinguishes it in spirit from a permanent delete. It never names drive_delete_file, so the sibling distinction is implied rather than stated.

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 parenthetical "(recoverable for 30 days)" hints at when to prefer this over a hard delete, but there is no explicit when-to-use, no prerequisites, and no named alternative among the siblings (drive_delete_file is the obvious one).

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