Skip to main content
Glama

Update team member profile

update_user_profile
DestructiveIdempotent

Update a team member's organization-profile fields: first name, last name, country, timezone, and job title. Only the fields you provide are changed (PATCH semantics). Role changes are not supported here — use the dedicated role-change tool. The organization is fixed by your context — never pass an organization id. You cannot target a user more privileged than yourself.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "org_user_id": "<org_user_id>"
    },
    "name": "update_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoUpdated country.
timezoneNoUpdated timezone (IANA or Windows id).
job_titleNoUpdated job title.
last_nameNoUpdated last name.
first_nameNoUpdated first name.
org_user_idYesId of the OrganizationUser to update.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real context beyond them by disclosing PATCH semantics (only supplied fields change, nothing is cleared) and a privilege-ceiling restriction on the target. It stops short of explaining what 'destructive' means here or what the failure mode looks like when the privilege check rejects the call, so the destructive hint is only partially reconciled.

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?

Four tight sentences, each carrying a distinct constraint, with the field list and PATCH semantics front-loaded before the exclusions and safety rules. No filler or restatement of the title.

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 7-parameter mutation with no output schema, the description covers scope, partial-update semantics, sibling routing, and privilege limits — enough to call it correctly. Minor gaps remain around error/response behavior and what the destructive annotation implies for existing field values.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: the partial-update contract for the optional profile fields and the rule that org_user_id must belong to a user no more privileged than the caller. It does not discuss idempotency_key behavior, though the schema already documents it fully.

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?

States a specific verb and resource ('Update a team member's organization-profile fields') and enumerates exactly which fields are mutable (first name, last name, country, timezone, job title). It explicitly carves out role changes and points to a dedicated tool, so an agent can distinguish it from change_user_role and update_user_preferences without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-not guidance ('Role changes are not supported here — use the dedicated role-change tool') plus two hard invocation constraints: never pass an organization id, and you cannot target a user more privileged than yourself. These are exactly the conditions that determine correct selection and invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources