Skip to main content
Glama
moneyforward-i

Admina MCP Server

update_identity

Update an existing identity's attributes such as employee status, type, name, email, department, job title, custom fields, or manager using the identity ID.

Instructions

Update an existing identity. Pass identityId and any fields to update (employeeStatus, employeeType, displayName, primaryEmail, department, jobTitle, customFields, manager, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identityIdYesThe ID of the identity to update
employeeStatusNoExtended status of the employee
employeeTypeNoType of the employee
managementTypeNoManagement type of the employee
displayNameNoDisplay name of the employee
firstNameNoFirst name of the employee
lastNameNoLast name of the employee
primaryEmailNoPrimary email of the employee
secondaryEmailsNoSecondary emails of the employee
companyNameNoCompany name of the employee
workLocationNoWork location of the employee
departmentNoDepartment of the employee
jobTitleNoJob title of the employee
employeeIdNoEmployee ID of the employee
lifecycleNoLifecycle of the employee
noteNoNotes of the employee
customFieldsNoCustom fields of the employee
managerNoManager of the employee

Implementation Reference

  • The main handler function for 'update_identity'. Calls `client.makePutApiCall('/identity/{identityId}', ...)` with the body built by the toBody helper.
    export async function updateIdentity(params: UpdateIdentityParams) {
      const client = getClient();
      const { identityId, ...rest } = params;
      return client.makePutApiCall(`/identity/${identityId}`, toBody(rest));
    }
  • Helper function `toBody` that extracts all updatable fields from input params (excluding identityId) and returns them as a Record for the PUT request body.
    function toBody(params: Omit<UpdateIdentityParams, "identityId">): Record<string, unknown> {
      const body: Record<string, unknown> = {};
      if (params.employeeStatus !== undefined) body.employeeStatus = params.employeeStatus;
      if (params.employeeType !== undefined) body.employeeType = params.employeeType;
      if (params.managementType !== undefined) body.managementType = params.managementType;
      if (params.displayName !== undefined) body.displayName = params.displayName;
      if (params.firstName !== undefined) body.firstName = params.firstName;
      if (params.lastName !== undefined) body.lastName = params.lastName;
      if (params.primaryEmail !== undefined) body.primaryEmail = params.primaryEmail;
      if (params.secondaryEmails !== undefined) body.secondaryEmails = params.secondaryEmails;
      if (params.companyName !== undefined) body.companyName = params.companyName;
      if (params.workLocation !== undefined) body.workLocation = params.workLocation;
      if (params.department !== undefined) body.department = params.department;
      if (params.jobTitle !== undefined) body.jobTitle = params.jobTitle;
      if (params.employeeId !== undefined) body.employeeId = params.employeeId;
      if (params.lifecycle !== undefined) body.lifecycle = params.lifecycle;
      if (params.note !== undefined) body.note = params.note;
      if (params.customFields !== undefined) body.customFields = params.customFields;
      if (params.manager !== undefined) body.manager = params.manager;
      return body;
    }
  • Zod schema `UpdateIdentitySchema` defining all input fields: identityId (required), employeeStatus, employeeType, managementType, displayName, firstName, lastName, primaryEmail, secondaryEmails, companyName, workLocation, department, jobTitle, employeeId, lifecycle, note, customFields, manager.
    export const UpdateIdentitySchema = z.object({
      identityId: z.string().describe("The ID of the identity to update"),
      employeeStatus: EmployeeStatusEnum.optional().describe("Extended status of the employee"),
      employeeType: EmployeeTypeEnum.optional().describe("Type of the employee"),
      managementType: ManagementTypeEnum.nullable().optional().describe("Management type of the employee"),
      displayName: z.string().nullable().optional().describe("Display name of the employee"),
      firstName: z.string().optional().describe("First name of the employee"),
      lastName: z.string().optional().describe("Last name of the employee"),
      primaryEmail: z.string().nullable().optional().describe("Primary email of the employee"),
      secondaryEmails: z.array(z.string()).nullable().optional().describe("Secondary emails of the employee"),
      companyName: z.string().nullable().optional().describe("Company name of the employee"),
      workLocation: z.string().nullable().optional().describe("Work location of the employee"),
      department: DepartmentSchema.nullable().optional().describe("Department of the employee"),
      jobTitle: z.string().nullable().optional().describe("Job title of the employee"),
      employeeId: z.string().nullable().optional().describe("Employee ID of the employee"),
      lifecycle: LifecycleSchema.optional().describe("Lifecycle of the employee"),
      note: z.string().nullable().optional().describe("Notes of the employee"),
      customFields: z.record(z.string(), z.unknown()).optional().describe("Custom fields of the employee"),
      manager: ManagerSchema.optional().describe("Manager of the employee"),
    });
  • src/index.ts:177-182 (registration)
    Registers the 'update_identity' tool with its description and inputSchema in the list of tools.
    {
      name: "update_identity",
      description:
        "Update an existing identity. Pass identityId and any fields to update (employeeStatus, employeeType, displayName, primaryEmail, department, jobTitle, customFields, manager, etc.).",
      inputSchema: zodToJsonSchema(UpdateIdentitySchema),
    },
  • src/index.ts:310-310 (registration)
    Maps the 'update_identity' tool name to the handler function, parsing input with UpdateIdentitySchema.
    update_identity: async (input) => updateIdentity(UpdateIdentitySchema.parse(input)),
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'update' but does not mention behavior on non-existent identity, permission requirements, return value, or side effects. Minimal transparency.

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 a single sentence that states purpose upfront. It is concise but could be structured with additional context in a second sentence. No wasted words.

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?

Despite high parameter coverage, the tool is complex (18 params, nested objects, no output schema). The description lacks details on return value, error handling, or behavioral context. Incomplete for effective use.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all 18 parameters. The description lists example fields but adds no new meaning beyond what is already in the schema. No compensation needed.

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

Purpose4/5

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

The description clearly states the verb 'update' and resource 'identity', and distinguishes from create/delete siblings. However, it does not explicitly differentiate from bulk_update_identities.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like archive_identity, delete_identity, or bulk_update_identities. The description only states what the tool does without any context on usage conditions.

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/moneyforward-i/admina-mcp-server'

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