Skip to main content
Glama

audit_shortcuts

Identify Google Drive shortcuts in a source folder that will break after migration, by checking if their targets will be in the Shared Drive. Outputs results to a Google Sheet.

Instructions

    Step 9 — Identify Google Drive shortcuts.

    Shortcuts pointing to files outside the migration scope will break
    after the move since they reference the original file's location.
    shortcutDetails returns the targetId and targetMimeType so you can
    determine whether the target will also be in the Shared Drive
    post-migration.

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

    GAM command:
        gam user <user_email> print filelist select <folder_id>
            showmimetype gshortcut
            fields "id,name,shortcutDetails,parents,owners"
            filepath excludetrashed
            todrive tdfileid <sheet_id> tdsheet "<sheet_name>"
            tdupdatesheet tdretaintitle 
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
folder_idYes
sheet_nameNoshortcuts
user_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses the tool returns targetId and targetMimeType via shortcutDetails, filters for shortcuts, excludes trashed items, and outputs to a Google Sheet. It fully explains behavioral traits without needing annotations.

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 the purpose and includes necessary context, arguments, and a GAM command. It is slightly lengthy but every sentence contributes value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, parameters, behavior (output to sheet, fields returned), and usage context (migration step). With an output schema present, it sufficiently explains return values.

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?

Each parameter is described in the Args section: user_email (owner of source folder), folder_id (ID of source folder), sheet_id (ID of Google Sheet), sheet_name (tab name, default). This adds significant meaning beyond the schema, compensating for 0% schema description coverage.

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 'Identify Google Drive shortcuts' with a specific verb and resource. It explains the context of migration, making it distinct from sibling audit tools.

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 places the tool in a migration workflow (Step 9) and explains why it's needed (shortcuts will break). It provides clear context but does not explicitly state when not to use or mention 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