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
DestructiveIdempotent

Update a Drive file by renaming, moving to a folder, or trashing/untrashing it. Provide fileId; use delete_drive_file for permanent deletion.

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.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds non-obvious behavior: that trash:false restores, that moving OUT of the old folder requires removeFromFolderId, and that permanent deletion lives elsewhere. This is genuine value beyond the annotations, though it does not describe the response shape.

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?

Front-loads the core purpose and packs the three modes and the sibling pointer into three tight sentences; every parenthetical earns its place with no redundant restatement of the schema.

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?

For a 5-param mutation tool with no output schema, the description covers all operations, parameter roles, reversibility, and the delete alternative. Full marks would require a note on what the updated file response contains, but that is minor here.

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 the baseline is 3, but the description adds relational meaning the schema does not: name implies rename, moveToFolderId pairs with removeFromFolderId to fully relocate, and trash is a tri-state-ish toggle. This extra semantic framing lifts it above baseline.

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 (update) and resource (Drive file) and enumerates the three distinct modes: rename, move, trash/untrash. It names the sibling delete_drive_file as the permanent-delete alternative, so an agent can distinguish them without opening schemas.

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?

Explains when each mode applies (rename via name, move via moveToFolderId/removeFromFolderId, trash boolean) and explicitly routes permanent deletion to delete_drive_file. It lacks an explicit note on when to prefer update_onedrive_file or how this differs from save_to_drive, which is the only gap.

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