Skip to main content
Glama
Sign In
mcp-google-drive

mcp-google-drive

by Longtran2404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_file

Delete a file from Google Drive. Optionally, permanently remove it instead of moving to trash.

Instructions

Delete a file from Google Drive

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

Input Schema

NameRequiredDescriptionDefault
fileIdYesID of the file to delete
permanentNoPermanently delete the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only says 'delete'. It omits whether files go to trash or are permanently deleted (only hinted via schema parameter 'permanent'), and no mention of auth needs or consequences.

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?

Single sentence with no unnecessary words. Highly concise and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite low complexity, the description fails to explain behavior (e.g., trash vs permanent), return values (none), or any side effects. For a deletion tool, more context is expected.

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 schema already describes parameters. The description adds no extra meaning beyond what the schema provides, meeting the baseline.

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 description clearly states the verb 'delete' and resource 'file from Google Drive'. It is specific but does not differentiate from sibling tools like 'move_file' or 'copy_file'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No prerequisites, exclusions, or context on appropriate scenarios provided.

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