Skip to main content
Glama

update_user

Idempotent

Update an existing user's profile details, including name, email, address, and custom properties.

Instructions

Update a user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the user to update
first_nameNoFirst name of the user.
middle_nameNoMiddle name of the user.
last_nameNoLast name of the user.
emailNoThe e-mail of the user. For admin users this field is ignored due to security concerns.
localeNo
wants_newsletterNoBoolean representing the possibility of the user to receive newsletters.
with_authenticationNoIf the user should be able to login and thus receive login details by mail. Only relevant when creating the user.
customNoThe custom properties of the user.
address_attributesNo
invoice_address_attributesNo
label_idsNoIDs of the labels
Behavior2/5

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

Description adds no behavioral context beyond annotations; does not mention side effects like email being ignored for admin users or any other traits.

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

Conciseness3/5

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

Very concise but lacks structure and valuable content; one sentence is minimal but not overly informative.

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

Completeness1/5

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

For a tool with 12 parameters, nested objects, and no output schema, the description is grossly insufficient; no mention of return values, behavior, or use context.

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 description coverage is 75%, so baseline is 3; description provides no parameter information, relying entirely on schema.

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 'Update a user.' clearly states the action and resource, but does not differentiate from sibling update tools like update_account or update_course.

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 versus alternatives; no context, preconditions, or exclusions provided.

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/martijnpieters/eduframe-mcp'

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