Skip to main content
Glama

build_bulk_gam_command

Constructs a GAM bulk processing command from structured inputs without executing it, returning the command string for review and later execution.

Instructions

Constructs a GAM bulk processing command from structured inputs without executing it.
Returns the full command string for review. Pass the args to validate_gam_command,
then run_gam_command if valid.

gam_command_template uses ~ColumnName for standalone column values and
~~ColumnName~~ when embedded within a larger string argument.
Example: ["update", "user", "~primaryEmail", "ou", "/Staff/~~Department~~"]

Use processing_mode 'loop' for rate-sensitive or ordered operations.
Use 'csv' for parallelized operations. Use 'tbatch' when nesting 'gam csv' inside a batch file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_rowsNo
sheet_nameNo
skip_fieldNo
match_fieldNo
source_typeYes
skip_patternNo
match_patternNo
sheet_file_idNo
show_commandsNo
operator_emailNo
local_file_pathNo
processing_modeYes
gam_command_templateYes
redirect_to_sheet_idNo
redirect_to_local_pathNo
redirect_to_sheet_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Explains non-execution and template syntax. No annotations, so description carries burden. Does not cover side effects, auth, or error handling, but adequate for a command-builder.

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?

Two concise paragraphs plus example. Well-structured, no fluff. Could be slightly more readable, but effective.

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

Completeness2/5

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

Given 16 parameters and no schema descriptions, description has major gaps. Workflow and key params covered, but many params unexplained. Output schema exists but not shown; still incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 0% so description must compensate. Only explains gam_command_template and processing_mode. Leaves 13 parameters undocumented (source_type, max_rows, etc.). Example helps but insufficient.

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?

Clearly states it constructs a GAM bulk command without executing, returns command string for review. Distinguishes from sibling tools validate and run.

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?

Provides workflow: build then validate then run. Explains processing modes for different use cases (loop for rate-sensitive, csv for parallel, tbatch for nested). Lacks explicit when-not-to-use, but context is clear.

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