Skip to main content
Glama
ktibbs9417

GAM MCP Server

by ktibbs9417
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

audit_file_inventory

Audits every file and folder under a specified Google Drive folder, exporting full metadata including file path, owners, sizes, and timestamps to a Google Sheet.

Instructions

    Step 2 — Master file/folder inventory.

    Prints every file and folder under the source folder with full
    metadata and resolved file paths, then writes the results to the
    specified Google Sheet tab.

    Fields returned: id, name, mimeType, owners, parents, size,
    modifiedTime, createdTime, trashed.  `filepath` resolves the full
    path from root.  `excludetrashed` omits deleted content.

    NOTE: If the user has not yet created a Google Sheet, instruct them
    to create one named "Migration Audit" with tabs: file_audit,
    all_permissions, file_count, own, not_owner, external_owner,
    public_files, shortcuts, shared_drive_members, migration_log,
    post_migration_permissions.

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

    GAM command:
        gam user <user_email> print filelist select <folder_id>
            fields "id,name,mimeType,owners,parents,size,modifiedTime,
            createdTime,trashed" filepath excludetrashed
            todrive tdfileid <sheet_id> tdsheet "<sheet_name>"
            tdupdatesheet tdretaintitle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
folder_idYes
sheet_nameNofile_audit
user_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4/5.0
Behavior3/5

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

With no annotations, the description must fully disclose behaviors. It states it prints and writes results, lists fields, and mentions excludetrashed. However, it does not clarify whether results overwrite or append to the sheet, nor does it address permissions, rate limits, or error handling.

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 overview, fields, note, args, and command. Though lengthy, it remains organized and front-loads key info. The detailed GAM command is helpful but adds verbosity.

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 (content unknown), the description covers core functionality, parameters, and fields returned. It lacks explicit edge-case handling but is sufficient for typical use.

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 compensates fully by explaining all four parameters (user_email, folder_id, sheet_id, sheet_name) with details on defaults and purpose. The GAM command verifies the mapping.

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 file/folder inventory under a source folder, prints metadata, and writes to a Google Sheet. The title 'audit_file_inventory' and the step labeling 'Master file/folder inventory' strongly distinguish it from sibling tools like audit_all_permissions or audit_file_counts, which focus on specific audits.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this is Step 2 in a process, suggesting an ordering, but it does not explicitly instruct when to use this tool versus others. It includes a note about creating the sheet, but lacks guidance on alternatives or when not to use.

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