Skip to main content
Glama

update_user

Modifies user details in Zoom, including name, user type, timezone, and meeting preferences, using the specified user ID for identification through the Zoom API MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deptNoDepartment
first_nameNoUser's first name
last_nameNoUser's last name
pmiNoPersonal Meeting ID
timezoneNoUser timezone
typeNoUser type
use_pmiNoUse Personal Meeting ID for instant meetings
user_idYesThe user ID or email address

Implementation Reference

  • The handler function implementing the update_user tool logic. It sends a PATCH request to the Zoom API to update the specified user's information.
    handler: async ({ user_id, ...userData }) => {
      try {
        const response = await zoomApi.patch(`/users/${user_id}`, userData);
        return handleApiResponse(response);
      } catch (error) {
        return handleApiError(error);
      }
    }
  • Zod schema defining the input parameters and validation for the update_user tool.
    schema: {
      user_id: z.string().describe("The user ID or email address"),
      first_name: z.string().optional().describe("User's first name"),
      last_name: z.string().optional().describe("User's last name"),
      type: z.number().min(1).max(99).optional().describe("User type"),
      pmi: z.string().optional().describe("Personal Meeting ID"),
      use_pmi: z.boolean().optional().describe("Use Personal Meeting ID for instant meetings"),
      timezone: z.string().optional().describe("User timezone"),
      dept: z.string().optional().describe("Department")
    },
  • src/server.js:47-47 (registration)
    Registers the usersTools array containing the update_user tool (among others) with the MCP server via the registerTools utility function.
    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