Skip to main content
Glama

audit_public_files

Identify publicly accessible files within a specified Google Drive folder and export results to a Google Sheet for security review.

Instructions

    Step 8 — Files accessible to "anyone with the link" or publicly.

    These are the highest-risk files from a security stand-point.
    Shared Drives can restrict this behaviour at the drive level, so
    you need to know what you are inheriting.

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
folder_idYes
sheet_nameNopublic_files
user_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or side effects. The provided GAM command suggests it writes to a sheet, but the description itself lacks behavioral clarity.

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 front-loaded with purpose and includes parameter details, but the large GAM command block is extraneous for an AI agent and could be shortened or moved to examples.

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 presence of an output schema, the description need not detail return values. It provides enough context about the tool's purpose and inputs, though it could clarify whether the tool returns data or solely writes to a sheet.

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?

Despite 0% schema description coverage, the description adds meaningful context for each parameter, e.g., 'user_email: The email of the user who owns the source folder.' This clarifies parameter roles beyond their names.

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 audits files accessible to 'anyone with the link' or publicly, labeling them as highest-risk. It distinguishes from siblings like audit_external_permissions and audit_all_permissions by focusing on public access specifically.

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 usage when assessing inherited public file risks, mentioning Shared Drives restrictions. However, it does not explicitly state when not to use this tool or provide alternative tools for similar tasks.

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