Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_move

Move a Google Drive file or folder to a new parent folder when reorganizing content by specifying the file ID and destination folder ID.

Instructions

Move a file or folder into another folder.

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": {
      "fileId": "<fileId>",
      "newParentId": "<newParentId>"
    },
    "name": "drive_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYes
newParentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond the annotations: it doesn't say that the item is removed from its prior parent, what happens with folders moved into descendants, or what errors occur on invalid parent IDs. A 3 reflects annotations doing most of the work with no extra behavioral context.

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?

One short sentence, front-loaded with the verb and free of padding. Brevity is appropriate, though it comes at the cost of the missing detail noted elsewhere rather than through deliberate economy.

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?

For a two-parameter mutation with no output schema and no parameter documentation, the description is thin. It should at minimum state that the item leaves its current parent, whether permissions or sharing carry over, and any restrictions such as not moving a folder into itself.

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 for both parameters. It implies fileId identifies the item and newParentId the destination folder, and clarifies that the item may be a folder, but it never explains ID formats, that a single new parent is accepted, or any constraints on the target.

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?

The description gives a specific verb plus resource ("Move a file or folder") and names the destination concept, so an agent can distinguish it from read-only siblings like drive_get_file or drive_list_folder. It stops short of explicitly contrasting it with drive_copy or drive_update_metadata, which is the only reason it isn't a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus alternatives, and no exclusions or prerequisites are stated. An agent must infer that drive_copy is the non-moving variant and that drive_update_metadata is the tool for changing other properties.

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