Skip to main content
Glama

reapply_user_group_permissions

Recreates user and group ACLs on Shared Drive files based on permissions from an audit sheet. Requires confirmation to execute.

Instructions

    Step 12 — Reapply user and group permissions from the audit sheet.

    DESTRUCTIVE — requires confirmed=True to execute.

    Reads the all_permissions sheet and re-creates every user/group ACL
    on the corresponding file in the Shared Drive.  Processes only
    rows where permission.type is "user" or "group".

    INFO: Ownership cannot be transferred via ACL on a Shared Drive.
    In Shared Drives the drive itself is the owner — owner-role rows
    from the audit sheet will be silently ignored.

    Args:
        user_email: The admin email executing the command.
        sheet_id: The ID of the Google Sheet containing the audit.
        sheet_name: The tab containing ACL data (default: "all_permissions").
        confirmed: Must be True to execute. False returns a preview.

    GAM command:
        gam config csv_input_row_filter "permission.type:regex:user|group"
            redirect stdout ./reapply_user_group_perms.txt multiprocess
            redirect stderr stdout
            csv gsheet <user_email> <sheet_id> <sheet_name>
            gam user <user_email> create drivefileacl "~id"
            "~permission.type" "~permission.emailAddress"
            role "~permission.role" nodetails
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
confirmedNo
sheet_nameNoall_permissions
user_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully covers behavior: destructive action, confirmed flag, ownership limitation in Shared Drives, and silent ignoring of owner-role rows. The GAM command provides exact operation details.

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

Conciseness3/5

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

The description is verbose, including a full GAM command and argument list that could be condensed. The first sentence is clear, but subsequent text could be more succinct.

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 an output schema present and thorough behavioral transparency, the description addresses most agent needs. It could mention the specific role of being 'Step 12' in a larger process, but overall complete.

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 0%, but description adds some meaning for 'confirmed' (must be True) and 'sheet_name' (default value). However, 'user_email' and 'sheet_id' lack additional context beyond their names.

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 reapplies user and group permissions from an audit sheet, differentiating it from sibling tools like reapply_anyone_permissions and reapply_domain_permissions by limiting to 'user' and 'group' types.

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 explains it processes only user/group permission types and requires confirmed=True for execution, implicitly guiding when to use it. However, it lacks explicit 'when not to use' or direct comparison to siblings.

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