Skip to main content
Glama
ktibbs9417

GAM MCP Server

by ktibbs9417
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

audit_all_permissions

Audit all file and folder permissions by listing every ACL entry, creating a master reference sheet for permission reapplication post-migration.

Instructions

    Step 6 — Full Access Control List audit.

    Lists every permission entry (one row per ACL) for every file and
    folder under the source.  This sheet is the master reference used
    by the permission-reapplication steps (12–14) after migration.

    basicpermissions returns: allowFileDiscovery, deleted, domain,
    emailAddress, expirationTime, id, role, type.

    Args:
        user_email: The email of the user who owns the source folder.
        folder_id: The ID of the source folder.
        sheet_id: The ID of the Google Sheet for output.
        sheet_name: The tab name (default: "all_permissions").

    GAM command:
        gam user <user_email> print filelist select <folder_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
folder_idYes
sheet_nameNoall_permissions
user_emailYes

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?

No annotations exist, so description carries full burden. It discloses output to a Google Sheet and lists returned fields, but lacks mention of performance implications, rate limits, or authentication requirements (beyond user_email).

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 structured with purpose, context, args, and a GAM command. While the command is long, it's relevant. Minimal fluff; could be slightly more concise but acceptable for a complex tool.

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, no annotations, output schema exists), the description provides enough context: it's step 6, writes to a sheet, and lists returned fields. Could mention prerequisites like GAM setup.

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 coverage is 0%, but description has an 'Args:' section explaining each parameter, including defaults and usage in the GAM command. This adds significant meaning beyond schema titles.

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 it performs a full ACL audit listing every permission entry for files/folders under a source, and it's step 6 in a migration workflow. This differentiates it from sibling audit tools that filter (external, public, etc.).

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?

It positions itself as 'Step 6' and 'master reference for reapplication steps', implying it runs after earlier steps and before reapplication. However, it does not explicitly list when to use vs alternative audit tools or provide exclusion criteria.

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