fastmcp-gsuite

by tumf

Overview Schema Source Related Servers Discussions Admin

Python

Remote

move_drive_folder

Move a Google Drive folder to a new parent folder. By default, the folder is removed from its original location.

Instructions

Move a folder to a different location in Google 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": {
      "user_id": "<user_id>",
      "folder_id": "<folder_id>",
      "new_parent_id": "<new_parent_id>"
    },
    "name": "move_drive_folder"
  }
}

Input Schema

Name	Required	Description
`user_id`	Yes	The EMAIL of the Google account. Choose from:
`folder_id`	Yes	ID of the folder to move.
`new_parent_id`	Yes	ID of the destination folder.
`remove_previous_parents`	No	Whether to remove the folder from its current parent. If False, the folder will be in multiple locations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 21, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as permission requirements, reversibility, or the effect of the 'remove_previous_parents' parameter. The minimal description leaves significant behavior undocumented.

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?

The description is a single, front-loaded sentence of nine words. Every word is meaningful, and there is no wasted text. It is appropriately concise for a straightforward operation.

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?

Despite good schema coverage, the description lacks essential context: no output schema is specified, no prerequisites (e.g., how to obtain folder IDs), no error conditions, and no explanation of the dual-parenting behavior controlled by 'remove_previous_parents'. The tool is only partially documented.

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?

The schema already provides 100% coverage with clear descriptions for each parameter (user_id, folder_id, new_parent_id, remove_previous_parents). The tool description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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 'Move a folder to a different location in Google Drive' uses a specific verb ('Move') and clearly identifies the resource ('folder') and the action. It differentiates from sibling tool 'move_drive_file' by specifying 'folder', making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives like 'move_drive_file' for files, nor does it mention prerequisites (e.g., needing folder IDs). No when-not-to-use or context for choosing this action is given.

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