Skip to main content
Glama

update_user

Modify user details, including name and email, within the TeamRetro platform using structured input for accurate and efficient updates.

Instructions

Update an existing user's information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesstring
emailAddressYesstring
nameYesstring

Implementation Reference

  • The core implementation of the 'update_user' tool, including its input schema (Zod), description, and handler function that delegates to usersService.updateUser.
    update_user: { schema: z.object({ email: emailSchema, name: nameSchema.optional(), emailAddress: emailSchema, }), description: "Update an existing user's details, such as their name and emailAddress, by providing their current email", handler: async (args: { email: string; name?: string | null; emailAddress?: string; }) => createToolResponse( usersService.updateUser(args.email, { name: args.name, emailAddress: args.emailAddress, }) ), },
  • src/tools.ts:13-22 (registration)
    Registers the 'update_user' tool by importing and spreading userTools into the central tools object, which is then used to generate toolSchema and toolHandlers for MCP.
    const tools = { ...userTools, ...teamTools, ...teamMembersTools, ...actionTools, ...retrospectiveTools, ...agreementTools, ...healthModelTools, ...healthCheckTools, };
  • Supporting service method 'updateUser' that executes the PATCH API request to update user details.
    async updateUser( email: string, updateData: { name?: string | null; emailAddress?: string } ): Promise<SingleApiResponse<User>> { return this.patch<SingleApiResponse<User>>(`/v1/users/${email}`, { body: updateData, }); }

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/adepanges/teamretro-mcp-server'

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