Skip to main content
Glama
Sign In
drive-mcp

drive-mcp

by reisbel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

trash_file

Move a Google Drive file or folder to the trash without permanent deletion. Recover it within 30 days if needed.

Instructions

WRITES. Move a file or folder to the trash. Reversible with untrash_file for 30 days; nothing is permanently deleted.

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

Input Schema

NameRequiredDescriptionDefault
fileIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well by flagging 'WRITES.' and disclosing reversibility for 30 days and that nothing is permanently deleted. It omits permission/auth requirements and any non-obvious side effects, keeping it short of a 5.

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?

Three short clauses, front-loaded with the write signal, and no filler. Every sentence adds essential information about operation and reversibility.

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 one-parameter write tool with no annotations or output schema, the description covers purpose and important reversibility behavior. However, it leaves the sole required parameter undocumented, so an agent still lacks guidance on what fileId should contain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required fileId parameter, and the description never names or explains fileId's expected format. It only implies the ID can refer to a file or folder; that is minimal compensation for the missing schema documentation.

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?

States a specific verb and resource ('Move a file or folder to the trash') and immediately distinguishes the operation from its inverse by naming untrash_file. An agent can identify the tool's job without reading the schema.

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

Usage Guidelines4/5

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

Provides clear context for when the tool applies (reversible trashing) and names untrash_file as the restoration alternative. It does not explicitly state exclusions or when not to use this versus permanent delete, but the reversible window supplies useful selection context.

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