Skip to main content
Glama

edit_user

Update specific user fields—name, email, department, approver, and more—without affecting other details.

Instructions

Edit a user. Only the fields you supply are changed (partial update).

Args: user_id: The ID of the user to edit. email_address: New email. Pass "" to clear an existing address. approver_id: The user's approver; set to 0 to default to dept manager. public_holiday_set_id: Public holiday set (needs has_public_holidays). has_public_holidays: Enable public holidays for this user. (Other args map directly to the corresponding user fields.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
adminNo
countryNo
user_idYes
address1No
address2No
birthdayNo
directorNo
job_titleNo
last_nameNo
post_codeNo
first_nameNo
payroll_idNo
start_dateNo
telephone1No
telephone2No
approver_idNo
department_idNo
email_addressNo
has_public_holidaysNo
public_holiday_set_idNo
emergency_contact_nameNo
emergency_contact_phoneNo
Behavior2/5

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

With no annotations, description must disclose behavior. It notes partial update but omits side effects, authentication needs, error handling, or success/failure responses.

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?

Starts with a clear, front-loaded purpose. The Arg list is somewhat redundant given the schema, but overall efficient.

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?

High parameter count and no output schema demand thorough description. Missing validation, constraints, return value, and permissions. Incomplete for safe invocation.

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

Parameters2/5

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

Schema coverage is 0%, yet description covers only 5 of 23 parameters with specific notes (e.g., email_address can be cleared). The rest are dismissed as 'map directly' without further detail.

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 'Edit a user' with partial update semantics. It distinguishes from sibling tools like 'add_user' (create) and 'archive_user' (archive).

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

Usage Guidelines3/5

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

Implies usage when editing an existing user, but does not explicitly state when to use vs. alternatives (e.g., add_user for creation). No exclusion criteria or prerequisites mentioned.

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/mlequime/timetastic-mcp'

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