Skip to main content
Glama

update_user

Update an existing user's profile, permissions, and rates. Only the fields you provide are modified.

Instructions

Update an existing user's profile, permissions, and rates. Only provided fields will be updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the user to update (required)
first_nameNoUpdate first name
last_nameNoUpdate last name
emailNoUpdate email address
telephoneNoUpdate phone number
timezoneNoUpdate timezone
has_access_to_all_future_projectsNoUpdate future project access
is_contractorNoUpdate contractor status
is_adminNoUpdate admin privileges
is_project_managerNoUpdate project manager role
can_see_ratesNoUpdate rate visibility
can_create_projectsNoUpdate project creation permission
can_create_invoicesNoUpdate invoice creation permission
is_activeNoUpdate active status
weekly_capacityNoUpdate weekly capacity
default_hourly_rateNoUpdate default hourly rate
cost_rateNoUpdate cost rate
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It reveals the partial-update behavior ('Only provided fields will be updated') but omits details about required permissions, whether the update is reversible, or what response to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence that imparts both the purpose and a key behavioral detail (partial updates). Every word serves a purpose with no redundancy.

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

Completeness3/5

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

Given the large number of parameters (17) and the absence of an output schema, the description is adequate but minimal. It covers the core action and partial update behavior but leaves out expected return values, error handling, or idempotency, which would improve completeness for an agent.

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?

The input schema covers all 17 parameters with descriptions, achieving 100% coverage. The description adds no additional parameter-level detail beyond grouping them as 'profile, permissions, and rates,' which is marginally helpful.

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 the action (update), the target (existing user), and scope (profile, permissions, rates). The phrase 'Only provided fields will be updated' clarifies the semantics, distinguishing it from sibling tools like create_user or delete_user.

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?

The description does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. However, the name and sibling context make the intended use case (modifying an existing user) relatively 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/ianaleck/harvest-mcp-server'

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