Skip to main content
Glama
ktibbs9417

GAM MCP Server

by ktibbs9417
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

audit_post_migration_permissions

Audit a destination Shared Drive post-migration to confirm ACLs match pre-migration records, outputting results to a Google Sheet for verification.

Instructions

    Step 15 — Post-migration permissions audit on the Shared Drive.

    After reapplying permissions (steps 12–14), run this final audit
    against the Shared Drive to confirm the ACLs match what was
    recorded pre-migration.  Compare this tab against the
    all_permissions tab to verify correctness.

    Args:
        user_email: The admin email executing the command.
        shared_drive_id: The ID of the destination Shared Drive.
        sheet_id: The ID of the Google Sheet for output.
        sheet_name: The tab name (default: "post_migration_permissions").

    GAM command:
        gam user <user_email> print filelist select <shared_drive_id>
            fields "id,name,mimeType,basicpermissions,owners"
            filepath excludetrashed oneitemperrow pmfilter
            todrive tdfileid <sheet_id> tdsheet "<sheet_name>"
            tdupdatesheet tdretaintitle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
sheet_nameNopost_migration_permissions
user_emailYes
shared_drive_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It details the GAM command and output, but does not explicitly state read-only nature, authentication requirements, or potential side effects. The admin email is noted, but no mention of destructive capability or rate limits.

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 a bold step number, explanation, Args list, and a GAM command. It is fairly concise considering the detail needed, though the command block adds length.

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 existence of an output schema, the description adequately covers purpose, usage, parameters, and workflow. It mentions the output tab and comparison with all_permissions, making it complete for a migration audit tool.

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?

Schema description coverage is 0%, but the description enumerates all four parameters with their roles (admin email, destination drive, sheet ID, tab name) and includes the GAM command showing usage. It adds meaning beyond the schema, though format constraints are not specified.

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 identifies the tool as a post-migration permissions audit on a Shared Drive. It specifies the step number and workflow context, which distinguishes it from siblings like audit_all_permissions by emphasizing its role as a final verification step.

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 states when to use it ('After reapplying permissions (steps 12–14)') and how it relates to sibling tools ('Compare this tab against the all_permissions tab'). It provides clear context but does not explicitly exclude other scenarios or alternatives.

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