Skip to main content
Glama

create_user

Create and manage Zoom users by specifying actions like create, autoCreate, custCreate, or ssoCreate. Input user details such as email, type, first name, last name, and password to streamline user setup and administration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to create user
user_infoYesUser information

Implementation Reference

  • The handler function that executes the create_user tool logic by posting user creation data to the Zoom API /users endpoint.
    handler: async ({ action, user_info }) => {
      try {
        const response = await zoomApi.post('/users', { action, user_info });
        return handleApiResponse(response);
      } catch (error) {
        return handleApiError(error);
      }
    }
  • Zod schema defining the input parameters for the create_user tool: action enum and user_info object with email, type, names, and optional password.
    schema: {
      action: z.enum(["create", "autoCreate", "custCreate", "ssoCreate"]).describe("Action to create user"),
      user_info: z.object({
        email: z.string().email().describe("User email address"),
        type: z.number().min(1).max(99).describe("User type (1: Basic, 2: Licensed, 3: On-prem)"),
        first_name: z.string().optional().describe("User's first name"),
        last_name: z.string().optional().describe("User's last name"),
        password: z.string().optional().describe("User password")
      }).describe("User information")
    },
  • The complete definition of the create_user tool object within the usersTools array, including name, description, schema, and handler, which is exported for registration.
    {
      name: "create_user",
      description: "Create a new user on the account",
      schema: {
        action: z.enum(["create", "autoCreate", "custCreate", "ssoCreate"]).describe("Action to create user"),
        user_info: z.object({
          email: z.string().email().describe("User email address"),
          type: z.number().min(1).max(99).describe("User type (1: Basic, 2: Licensed, 3: On-prem)"),
          first_name: z.string().optional().describe("User's first name"),
          last_name: z.string().optional().describe("User's last name"),
          password: z.string().optional().describe("User password")
        }).describe("User information")
      },
      handler: async ({ action, user_info }) => {
        try {
          const response = await zoomApi.post('/users', { action, user_info });
          return handleApiResponse(response);
        } catch (error) {
          return handleApiError(error);
        }
      }
    },
  • src/server.js:47-47 (registration)
    Registers the usersTools array (containing create_user) by calling registerTools, which invokes server.tool for each tool.
    registerTools(usersTools);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Related 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/mattcoatsworth/zoom-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server