Skip to main content
Glama

Coline

Rename or move a file

update_drive_file
Idempotent

Renames, recolors or moves a file or folder, within its drive or (files only) to another 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": {
      "workspace": "<workspace>",
      "fileId": "<fileId>"
    },
    "name": "update_drive_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
colorNo
fileIdYesFile or folder id from list_drive_files, search or fetch.
driveIdNoMove it to this drive.
parentIdNoMove it into this folder; null for the drive's top level.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
fileYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare idempotent=true, destructive=false, and readOnlyHint=false, so safety is largely covered. The description adds genuinely new behavior in the files-only cross-drive constraint, but says nothing about whether omitted fields stay unchanged, what happens on name collisions or permission failures, or whether a move changes file identity/shares.

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?

A single well-formed sentence that front-loads the operations and closes with the one non-obvious constraint. No filler or redundant restatement of the title.

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?

With annotations covering idempotency and safety and an output schema present, the definition needs mainly to explain semantics and constraints, which it does. It stops short on prerequisite permissions (edit access), conflict behavior, and whether partial updates leave other fields intact.

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 67% and the description maps its verbs onto the name, color, and driveId/parentId parameters, and importantly clarifies that driveId is files-only. It does not explain that parentId=null means the drive top level (schema does) or that unspecified parameters are left untouched, so it adds only modest meaning beyond the schema.

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?

States three specific verbs (renames, recolors, moves) and the exact resource (file or folder), plus a useful scope constraint: cross-drive moves are files-only. An agent can distinguish it from rename_drive and copy_drive_file by the resource named, though no sibling is explicitly called out.

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 when to reach for this tool via the operation list, and the parenthetical 'files only' clarifies a boundary case for cross-drive moves. It never says when to prefer rename_sheet/update_doc or when to use trash_drive_file instead, so usage remains inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources