Skip to main content
Glama

create_gws_user

Create a new Google Workspace user by providing name, email, org unit, and password, with option to force password change on first login.

Instructions

    Creates a new Google Workspace user.
    
    Args:
        first_name: The first name of the user.
        last_name: The last name of the user.
        primary_email: The primary email address for the new user.
        org_unit_path: The organizational unit path (e.g., '/Staff/Engineering').
        password: The initial password for the user.
        change_password_at_next_login: Whether to force password change on first login.
        confirmed: Must be True to execute. If False, returns a preview.
        
    GAM pattern:
        gam create user <primary_email> firstname <first_name> lastname <last_name>
            org <org_unit_path> password <password> changepassword <true/false>
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYes
confirmedNo
last_nameYes
first_nameYes
org_unit_pathYes
primary_emailYes
change_password_at_next_loginNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description discloses the preview behavior via 'confirmed' parameter, but does not cover other behavioral traits such as error handling (e.g., duplicate user) or idempotency. No annotations are present, so the description carries the burden but falls short.

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 concise, starting with a clear purpose then listing parameters and a GAM pattern. It is front-loaded and avoids unnecessary detail, though the parameter list is somewhat redundant with the schema.

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 schema has no descriptions and no annotations, the description covers all parameters and the preview behavior, but lacks information about outcomes (e.g., whether the user already exists) or prerequisites. An output schema exists, so return value explanation is not needed.

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?

With 0% schema description coverage, the description adds meaningful explanations for each parameter (e.g., 'first_name: The first name of the user.'). This compensates well for the lack of schema descriptions, though some parameters like password lack constraints.

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 'Creates a new Google Workspace user' with a specific verb and resource, and the list of parameters aligns with that purpose. It distinguishes from sibling tools which are largely audit or bulk processing tools.

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 provides a GAM pattern for context but does not explicitly state when to use this tool versus alternatives or when not to use it. The 'confirmed' parameter hints at a preview mode, but no explicit usage guidance is given.

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