Skip to main content
Glama

reapply_domain_permissions

Recreate domain-wide permissions on Shared Drive files using a Google Sheet audit. Restores ACLs with domain roles and file discovery settings.

Instructions

    Step 13 — Reapply domain-wide permissions from the audit sheet.

    DESTRUCTIVE — requires confirmed=True to execute.

    Reads the all_permissions sheet and re-creates every domain ACL on
    the corresponding file in the Shared Drive.  Includes the
    allowFileDiscovery setting so domain-wide visibility is preserved.

    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:domain"
            redirect stdout ./reapply_domain_perms.txt multiprocess
            redirect stderr stdout
            csv gsheet <user_email> <sheet_id> <sheet_name>
            gam user <user_email> create drivefileacl "~id"
            "~permission.type" "~permission.domain"
            role "~permission.role"
            allowfilediscovery "~permission.allowFileDiscovery"
            nodetails
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
confirmedNo
sheet_nameNoall_permissions
user_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses destructive behavior, the requirement for confirmed=True, and that it reads from a Google Sheet and recreates ACLs including allowFileDiscovery. Since no annotations are provided, the description carries the full burden, and it effectively communicates the key behavioral traits.

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 somewhat lengthy, including a full GAM command example. While important information is front-loaded (purpose, destructive note), the command block adds verbosity. It could be more concise without losing essential details.

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 complexity (4 parameters, destructive action), the description covers key aspects: purpose, destructive flag, preview capability, and parameter roles. It does not detail the output schema, but that is provided elsewhere. Overall, it is sufficiently complete for an agent to decide usage.

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

Parameters4/5

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

With 0% schema description coverage, the description's 'Args' section provides meaning for each parameter: user_email, sheet_id, sheet_name (with default), and confirmed (with behavior explanation). This adds significant value beyond the schema's bare properties.

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 'Reapply domain-wide permissions from the audit sheet', specifying the verb 'reapply', the resource 'domain permissions', and the context 'from the audit sheet'. It differentiates from sibling tools like 'reapply_anyone_permissions' and 'reapply_user_group_permissions' by explicitly targeting domain permissions.

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 notes that it is destructive and requires confirmed=True to execute, providing a preview when confirmed=False. It implies usage in a multi-step process (Step 13) but does not explicitly state when to use this tool over alternatives like reapply_anyone_permissions.

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