Skip to main content
Glama

drive move file

drive_move_file

Move a Google Drive file to a new parent folder by updating only its metadata, optionally removing the old parent, to reorganize files without changing content.

Instructions

Move a Drive file to a new parent folder. Metadata-only change.

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": {
      "file_id": "<file_id>",
      "add_parent": "<add_parent>"
    },
    "name": "drive_move_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes
add_parentYes
remove_parentNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is partly covered. The description adds genuine value beyond them by clarifying that only metadata changes and the file's content is untouched, which is exactly the reassurance an agent needs before a move. It does not mention permission requirements or the two-parent outcome when remove_parent is omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action before the qualifier. Nothing is wasted, though the brevity comes at the cost of the parameter explanation the schema lacks.

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?

An output schema exists so return values need no explanation, but for a three-parameter tool with zero schema coverage the description leaves the optional remove_parent parameter entirely unexplained. An agent can guess the happy path but not the semantics of the optional argument.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it only loosely maps to add_parent via "new parent folder." It says nothing about file_id format or, critically, what remove_parent does and what happens when it is left null (the file may end up with two parents).

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?

"Move a Drive file to a new parent folder" gives a specific verb and resource with the scope of the change, which distinguishes it from siblings like drive_copy_file, drive_rename_file, or drive_delete_file by implication. It stops short of naming an alternative explicitly, but the operation is 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 phrase "Metadata-only change" implies this is the right tool when reorganizing without touching content, but it never states when to use this versus drive_copy_file or drive_rename_file, nor when to supply remove_parent. Usage is only implied.

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