Skip to main content
Glama
ktibbs9417

GAM MCP Server

by ktibbs9417
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

audit_owned_files

Audits files owned by a specific user in a Google Drive folder to find items eligible for moving to a Shared Drive, and exports the list to a Google Sheet.

Instructions

    Step 4 — Files owned by the migrating user.

    Only files owned by the user can be *moved* (not just copied) to a
    Shared Drive.  This audit isolates those items.

    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: "own").

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
folder_idYes
sheet_nameNoown
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?

No annotations provided. Description includes a GAM command showing fields, excludetrashed, and output to Sheet, giving moderate behavioral insight. Does not mention authentication needs 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.

Conciseness3/5

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

Main description is concise, but the full GAM command is long and could be summarized. The structure is acceptable but not optimized for quick scanning.

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?

Output schema exists, so return values need not be detailed. Description covers purpose, parameters, and a detailed command. Could mention what the sheet columns will be, but sufficient for an 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?

All 4 parameters are described in the context of the GAM command, adding meaning beyond the sparse schema (0% coverage). For example, user_email is 'the email of the user who owns the source folder.'

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?

Clear statement: 'Step 4 — Files owned by the migrating user. ... This audit isolates those items.' Distinguishes purpose from siblings like audit_not_owned_files, specifying it identifies files that can be moved.

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?

Explicitly placed as Step 4 in a migration process, implying when to use. Not explicitly stating when not to use, but sibling tools list provides alternative audit options.

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