Skip to main content
Glama

superset_user_update

Update existing user details for name, email, and active status. Replace the full role list in one call.

Instructions

Update a user. Only pass the fields you want to change.

IMPORTANT: roles REPLACES the entire role list (does not append). To add a single role: get the current roles via user_get, add the new ID to the list, then pass the full list.

Args: user_id: ID of the user to update. first_name: New first name. last_name: New last name. email: New email (must be unique). roles: New list of role IDs (REPLACES all current roles). active: Activate/deactivate the account. confirm_roles_replace: Confirmation for role replacement (REQUIRED when passing roles).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
rolesNo
activeNo
user_idYes
last_nameNo
first_nameNo
confirm_roles_replaceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses critical behavior that roles REPLACES the entire list, not appends, and requires confirm_roles_replace. Also notes email uniqueness and the partial update semantics. These are key behavioral traits beyond schema.

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?

Well-structured with an opening imperative, an IMPORTANT callout, and a bulleted Args list. Every sentence provides essential information; no filler. At ~150 words, it is appropriately sized for a 7-parameter mutation tool.

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

Completeness5/5

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

The description covers all critical aspects: partial update, role replacement behavior, confirmation requirement, uniqueness constraint, and a workflow for adding roles. Given the tool's complexity and no annotations, this is complete enough for an agent to select and invoke correctly.

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

Parameters5/5

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

Schema has 0% description coverage, but the description's Args section explains each parameter in plain language, including the semantics of roles ('REPLACES all current roles'), confirm_roles_replace ('REQUIRED when passing roles'), and active ('Activate/deactivate the account'). This fully compensates for the schema's lack of descriptions.

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 'Update a user' and specifies partial update semantics ('Only pass the fields you want to change'). It distinguishes from sibling tools like user_create, user_delete, and user_get by focusing on modification of existing users. The role replacement caveat further clarifies the operation.

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?

Mentions that only fields provided are changed, implying usage for modifying existing users. Provides explicit alternative: 'get the current roles via user_get' when adding a single role. However, it does not explicitly state when not to use or compare to create/delete, so not a full 5.

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/bintocher/mcp-superset'

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