Skip to main content
Glama
Sign In
Google Drive MCP

Google Drive MCP

by EgCooper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_file

Delete a file or folder by moving it to Google Drive trash. Provide the file ID to remove.

Instructions

Mueve un archivo o carpeta a la papelera de Google Drive.

Args: file_id: ID del elemento a eliminar.

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

Input Schema

NameRequiredDescriptionDefault
file_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description must disclose behavior. It reveals a key behavioral trait: the operation is a soft delete (moves to trash), not a permanent deletion. This is useful and beyond what the raw schema provides, though it could mention side effects like ownership requirements or undoing.

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 description is one concise sentence plus a clear Args listing. No fluff; every line adds value. It is appropriately sized for a simple tool.

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?

The tool is simple and the description conveys the essential behavior (move to trash, accepts file/folder ID). While it doesn't explain return values or permissions, the presence of an output schema and low complexity keep it adequately complete.

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

Parameters4/5

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

Schema coverage is 0%, so the description must define the parameter. It does so with 'file_id: ID del elemento a eliminar', adding meaning by specifying that the element can be a file or folder. This goes slightly beyond the bare schema field.

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 clearly states the tool's function: 'Mueve un archivo o carpeta a la papelera de Google Drive' (moves a file or folder to Google Drive trash). This is a specific verb+resource+destination, and it distinguishes from sibling 'move_file' by specifying the trash as the target.

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 description implies usage (when you want to delete something) but does not explicitly state when to use this over alternatives like move_file or permanent deletion. It does not mention any exclusions or prerequisites, so usage guidance is only implicit.

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