Skip to main content
Glama
Sign In
MCP Google Multi-Account Server

MCP Google Multi-Account Server

by bkbaheti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

drive_trash_file

Move a file to trash in Google Drive by providing the account ID and file ID. Works with multiple Google accounts in the MCP server.

Instructions

Move a file to trash in 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": {
      "accountId": "<accountId>",
      "fileId": "<fileId>"
    },
    "name": "drive_trash_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesThe file ID to trash
accountIdYesThe Google account ID, alias, or email

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It merely states the action without disclosing side effects like reversibility, permission requirements, or whether trashing is permanent. This is a mutation tool, and the lack of behavioral context is a clear gap.

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 a single, concise sentence with zero wasted words. It is perfectly sized for the simple action it describes.

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 simple two-parameter tool with complete schema and no output schema, the description is minimally adequate. However, it could be more complete by noting the file is moved to the Drive trash (not permanently deleted) and possibly mentioning that the action is reversible.

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?

The input schema covers both parameters with clear descriptions (fileId, accountId), so schema coverage is 100%. The description adds no extra parameter info, but the baseline for high schema coverage is 3.

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 action ('Move') and the resource ('a file to trash in Google Drive'), making it distinct from siblings like drive_move_file or gmail_trash. It is specific and unambiguous.

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 usage is implied from the description; it's obvious you use this tool to trash a file. However, there is no explicit guidance on when to prefer this over alternatives or any exclusions.

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