Skip to main content
Glama

audit_not_owned_files

Audit files owned by other users in a specified folder to identify items that cannot be moved to a Shared Drive.

Instructions

    Step 5 — Files owned by others.

    Files owned by other users inside this folder structure will NOT
    transfer with a standard move to a Shared Drive.  The host should
    inform the requesting user which folders/files are affected and
    that those items cannot be migrated.

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
folder_idYes
sheet_nameNonot_owner
user_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations exist, so the description must carry full transparency. It explains that files won't transfer and outputs to a sheet, but does not mention required permissions, side effects, or safety aspects beyond what is implicit.

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 fairly detailed but structured: a clear purpose statement, explanation, parameter list, and GAM command example. It could be slightly more concise, but the structure aids understanding.

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 tool's complexity (4 params, migration context) and existence of an output schema, the description adequately explains the tool's function, parameters, and usage context. It does not detail return values, but the output schema covers that.

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 the description individually explains each parameter (user_email, folder_id, sheet_id, sheet_name) with context, adding meaning beyond the schema structure.

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 the tool audits files owned by others in a folder, with specific context about migration. It distinguishes from sibling tools like audit_owned_files by focusing on non-owned files.

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 indicates it is Step 5 in a migration process, implying a specific use case. However, it lacks explicit when-not-to-use guidance or comparisons to 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