nextcloud-agent

Delete user

nextcloud_delete_user

DestructiveIdempotent

Delete a Nextcloud user account and all associated files, with explicit confirmation required for this destructive operation.

Instructions

Delete one account and its files.

DELETE /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>"
    },
    "name": "nextcloud_delete_user"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Explicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.
`user_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.0Nov 7, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the bar is lower; the description still adds real value by disclosing that the account's files are destroyed too, which is the key consequence an agent needs. It omits irreversibility and permission/auth requirements, and it does not mention that the confirm flag exists (the schema carries that).

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?

One front-loaded sentence stating the action and its side effect, followed by a short endpoint reference. The endpoint line is marginal value for an agent choosing a tool but is short and harmless.

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?

For a destructive admin operation with no output schema, the description covers what is deleted but not the surrounding contract: irreversibility, required privileges, behavior when the user has shares or other objects, and what a successful response looks like. Annotations cover the safety profile, so the remaining gaps are moderate rather than critical.

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 50%: confirm is well documented in the schema, while user_id has no schema description and the tool description only reveals it as a URL path placeholder. That placeholder implies user_id is an account identifier rather than a display name, but no format, lookup path, or failure behavior is added.

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?

"Delete one account and its files" gives a specific verb plus resource and adds the blast radius (the user's files), which separates it from siblings like nextcloud_delete_item, nextcloud_delete_group and nextcloud_disable_user. It stops short of naming the non-destructive alternative (disable_user), so it is clear but not fully differentiated.

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?

There is no statement of when to use this versus nextcloud_disable_user, nextcloud_delete_group, or nextcloud_remove_user_from_group (a far safer sibling that only revokes group membership). No prerequisites such as admin rights or whether the account must be disabled first are mentioned.

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

Deploy Server