Skip to main content
Glama

execute_migration_move

Recursively move a folder tree into a destination Shared Drive, merging duplicate folders and overwriting older duplicate files. Copies folder permissions for merged and newly created folders.

Instructions

    Step 11 — Move the source folder tree to the Shared Drive.

    DESTRUCTIVE — requires confirmed=True to execute.

    Recursively moves the folder tree into the destination Shared Drive,
    merging duplicate folders and overwriting older duplicate files.
    Folder permissions are copied for both merged and newly created folders.

    NOTE: Run ALL audit steps (1–10) before executing this step.

    NOTE: CSV/todrive logging is not supported by `move drivefile`. To retain
    a record of the move, redirect stdout/stderr to a log file at the shell
    level, or run a `print filelist` audit step before and after migration.

    Args:
        user_email: The email of the folder owner (must be a Shared Drive
                    Manager/Organizer of the destination).
        folder_id: The ID of the source folder.
        shared_drive_id: The ID of the destination Shared Drive.
        confirmed: Must be True to execute. False returns a preview.

    GAM command:
        gam user <user_email> move drivefile <folder_id>
            teamdriveparentid <shared_drive_id>
            duplicatefiles overwriteolder
            duplicatefolders merge
            copymergedtopfolderpermissions true
            copymergedsubfolderpermissions true
            summary
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmedNo
folder_idYes
user_emailYes
shared_drive_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description bears full responsibility. It discloses destructiveness, the requirement for confirmed=True, merging behavior, permission copying, and logging limitations. It lacks some details like rate limits or full conditions for user_email, but the disclosed information is substantial and adequate.

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?

The description is well-structured with sections for purpose, destructive warning, notes, args, and a GAM command example. It is slightly lengthy but every sentence adds value. Front-loading the purpose and highlighting the destructive nature aids quick comprehension.

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?

Given the tool's complexity and the presence of an output schema, the description covers purpose, prerequisites, behavior, parameters, and logging alternatives. It does not explicitly describe the output format, but the GAM command example includes 'summary'. Overall, it provides sufficient context for correct usage.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate. It provides an 'Args' section explaining each parameter: user_email (must be Shared Drive Manager/Organizer), folder_id, shared_drive_id, and confirmed (False for preview). This adds crucial meaning beyond the schema's bare property definitions.

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 clearly states the tool's function: 'Move the source folder tree to the Shared Drive.' It provides specific details about merging duplicate folders and overwriting older duplicate files, distinguishing it from sibling audit tools that precede it.

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?

The description explicitly instructs to run all audit steps (1–10) before executing this step, indicating a clear prerequisite. It also notes the destructive nature and the need for confirmed=True. It does not explicitly state when not to use it, but the prerequisite implies proper usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ktibbs9417/gamcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server