Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Rename / move / trash a Drive file

update_drive_file
Idempotent

Rename, move, or trash a Google Drive file by providing its file ID. Set a new name, target folder, or trash status to update the file.

Instructions

Update a Drive file: rename (name), move it into a folder (moveToFolderId, optionally removeFromFolderId to move OUT of the old one), or trash / untrash it (trash:true|false). Pass fileId (from list_drive_files). To delete permanently, use delete_drive_file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNonew name
trashNotrue -> move to Trash; false -> restore from Trash
fileIdYesthe Drive file id
moveToFolderIdNofolder id to move the file into (from create_drive_folder / list_drive_files)
removeFromFolderIdNothe old parent folder id to remove (when moving)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.272
    • changedInput schema / properties / trash / description
      Previous value: -"true → move to Trash; false → restore from Trash"New value: +"true -> move to Trash; false -> restore from Trash"
  2. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "id": {
-      "type": "string"
-    },
-    "name": {
-      "type": "string"
-    },
-    "trashed": {
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Addedv0.1.15

TDQS

A4.5/5.0
Behavior4/5

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

The description clarifies behavior beyond annotations: trash:true|false means trash or restore, removeFromFolderId means moving OUT of the old parent, and permanent deletion is explicitly out of scope. Annotations already cover safety/idempotency, so the extra operational detail is meaningful.

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?

Two tightly written sentences convey all three operation modes, the relevant parameters, and the alternative for permanent deletion. Every clause earns its place and the main purpose is front-loaded.

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

Completeness5/5

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

For a multi-mode mutation tool with five parameters and no output schema, the description covers all operations, parameter semantics, input provenance, and the key exclusions. An agent has enough to invoke it correctly.

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 100%, so all parameters are already documented. The description adds value by explaining how parameters combine into operations (rename vs move vs trash) and where fileId should come from.

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 uses a specific verb-resource pairing ('Update a Drive file') and enumerates the exact operations: rename, move, trash/untrash. It also distinguishes itself from the permanent-deletion sibling by explicitly routing that use case to delete_drive_file.

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?

It tells the agent where fileId comes from (list_drive_files) and explicitly says permanent deletion should use delete_drive_file instead. It does not cover every alternative sibling, but it gives clear context for the main decision an agent needs to make.

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