Skip to main content
Glama
HR-Partner

HR Partner MCP Server

Official
by HR-Partner

Add or Update Employee

save_employee

Create or update an employee in HR Partner using the unique employee code. Only fields provided are modified, and new department, location, position, or status values are added automatically.

Instructions

Create a new employee or update an existing one in HR Partner (upsert by Employee Code). Only supplied fields are modified. Custom fields go in custom_data (only the keys you want to change are needed). New values for department/location/position/employment_status are added to the lookup lists automatically. Note: tags, contacts and addresses can be added/updated but NOT deleted via the API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe unique Employee Code. If it exists the employee is updated, otherwise a new employee is created
tagsNoArray of tag objects to allocate, e.g. [{"tag": "Full Timer"}]. New tags are created automatically
locationNoLocation the employee is in (new values are added to the dropdown options)
positionNoPosition or job title (new values are added to the dropdown options)
can_logonNoWhether the employee can log on to their employee portal (true/false)
full_nameNoCombined name of the employee (i.e. 'First Last' or 'Last, First')
is_activeNoWhether the employee is active in HR Partner (true/false)
last_nameNoSurname of the employee
pay_pointNoReference for the employee's pay point
departmentNoDepartment name the employee belongs to (new values are added to the dropdown options)
reports_toNoEmployee Code of the person this employee reports to
salutationNoGreeting/salutation used for the employee
started_atNoDate the employee started with the company (format yyyy-mm-dd)
tax_numberNoSSN, TFN, National ID or other tax identifier
custom_dataNoObject of custom field name -> value. Only included fields are updated. Tip: call get_employee on an existing employee to discover the custom field names.
finished_atNoDate the employee was terminated/left the company (format yyyy-mm-dd)
first_namesNoFirst (and optionally middle) name of the employee
date_of_birthNoEmployee's date of birth (format yyyy-mm-dd)
is_terminatedNoWhether the employee is terminated in HR Partner (true/false)
gender_identityNoM or F, or the full gender identity text if extended gender identities are enabled
portal_usernameNoEmployee's username for the portal
employee_contactsNoContact records to add or update
employment_statusNoEmployment status, i.e. Full Time, Part Time, Contractor etc.
employee_addressesNoAddress records to add or update
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses important behavioral traits: upsert semantics, partial update behavior, automatic addition of lookup values for certain fields, and the explicit limitation that 'tags, contacts and addresses can be added/updated but NOT deleted via the API'. This goes well beyond just stating the action.

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 four sentences, front-loaded with the primary purpose. Each sentence adds meaningful information: upsert behavior, partial update, custom_data handling, auto-add lookup values, and the deletion limitation. It is dense but not unnecessarily long for a tool with 24 parameters.

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

Completeness4/5

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

For a highly complex tool (24 parameters, no output schema, no annotations), the description covers the core semantics well: upsert by code, partial updates, custom fields, automatic lookup creation, and deletion limitations. It does not describe the return value or error behavior, but given the complexity and the guidance about how to discover custom fields, it is reasonably complete.

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?

The schema provides descriptions for all 24 parameters (100% coverage), so the baseline is 3. The description adds extra meaning: it explains that only supplied fields are modified, that custom_data only needs the keys to change, and that new values for department/location/position/employment_status are automatically added to lookup lists – all of which are not fully apparent from the schema descriptions alone.

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 'Create a new employee or update an existing one in HR Partner (upsert by Employee Code)' – a specific verb, resource, and semantics that distinguish it from sibling tools like save_applicant and save_application.

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

Usage Guidelines4/5

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

Provides key usage context: 'Only supplied fields are modified', 'Custom fields go in custom_data', and the tip to 'call get_employee on an existing employee to discover the custom field names'. It implies when to use (upsert an employee) but does not explicitly contrast with alternatives or state when not to use, though the guidance is fairly clear.

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/HR-Partner/hrpartner-mcp'

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