nextcloud-agent

Update user

nextcloud_update_user

Idempotent

Update a single field (email, display name, quota, password, phone, address, website, Twitter, language, or locale) for a Nextcloud user by passing the user ID, field key, and new value.

Instructions

Change one field of an account.

PUT /ocs/v2.php/cloud/users/{user_id}

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": {
      "user_id": "<user_id>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "nextcloud_update_user"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes
`value`	Yes
`user_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.0Nov 7, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare non-read-only, idempotent, non-destructive, and open-world behavior, but the description does not add operational context such as admin/auth requirements, whether password/quota changes have side effects, or what happens to unmentioned fields. The PUT endpoint line repeats the mutation method without expanding on it.

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?

Two short sentences, front-loaded with the core action, with no filler. The endpoint line is terse and arguably optional, but the definition is not bloated.

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?

For a user-mutation tool with three required parameters and no output schema, the definition is under-specified: it lacks permission requirements, field-specific value expectations, and confirmation of what is returned or changed. The existing annotations cover safety hints but not the operational details an agent needs for correct 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 description coverage is 0%, so the description needs to explain user_id, key, and value. It only says one field is changed; it does not clarify that key selects the field and value is the new setting, nor does it explain value formats for quota/password/locale.

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 gives a concrete verb ('Change') and scope ('one field of an account'), which is clearer than the title alone and rules out broad multi-field updates. It does not explicitly distinguish this from sibling user tools like create_user, delete_user, or get_user beyond the implied update operation.

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?

It implies the tool is for modifying an existing account, but never states when to use it versus create_user, delete_user, or a read/get tool. The one-field constraint is useful but is a scope note rather than explicit usage guidance.

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

Deploy Server