Skip to main content
Glama

bulk_process_from_sheet

Run bulk Google Workspace administrative commands by referencing a Google Sheet. Specify command templates with column placeholders, optionally filter rows, and redirect results to a sheet.

Instructions

    Executes a GAM bulk command using a Google Sheet as the data source.
    
    Args:
        operator_email: The email of the admin running the command (needs access to the sheets).
        sheet_file_id: The ID of the source Google Sheet.
        sheet_name: The tab name containing the source data.
        gam_command_template: List of command template fragments using ~ColumnName syntax.
        match_field: Optional column name to filter on.
        match_pattern: Optional regex pattern to match against match_field.
        redirect_to_sheet_id: Optional Sheet ID to write results to.
        redirect_to_sheet_name: Tab name for results.
        confirmed: Must be True to execute. If False, returns a preview.
        
    GAM pattern:
        [redirect csv - multiprocess todrive tdfileid <id> tdsheet "<name>" tdupdatesheet]
        csv gsheet <operator_email> <sheet_file_id> "<sheet_name>"
        [matchfield <match_field> <match_pattern>]
        gam <gam_command_template...>
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmedNo
sheet_nameYes
match_fieldNo
match_patternNo
sheet_file_idYes
operator_emailYes
gam_command_templateYes
redirect_to_sheet_idNo
redirect_to_sheet_nameNoBulk Output

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses preview/execute behavior via the confirmed parameter and mentions redirect capabilities, but does not warn about potential destructive actions from the GAM command or specify required permissions for operator_email.

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 reasonably concise and well-structured, with a clear purpose statement, an Args section, and a GAM pattern overview. It could be slightly more terse but effectively communicates essential information without excessive verbosity.

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

Completeness3/5

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

Given the complexity (9 parameters, bulk operation, output schema exists), the description covers parameter behavior and preview/execute logic well, but it does not explain the return values or output schema. It also omits error handling and limits, leaving gaps for an AI agent.

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%, so the description compensates well by explaining each parameter with context, e.g., operator_email needs sheet access and gam_command_template uses ~ColumnName syntax. The GAM pattern example provides additional clarity, though some parameter format details are omitted.

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 'Executes a GAM bulk command using a Google Sheet as the data source.' This is a specific verb and resource, differentiating it from siblings like run_gam_command (single command) and build_bulk_gam_command (command construction).

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 explains the tool's operation and parameters but does not explicitly state when to use this versus alternatives, nor does it provide conditions for not using it. The usage is implied by the name and description but lacks explicit guidance.

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