Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Remove user from group

nextcloud_remove_user_from_group
DestructiveIdempotent

Remove a Nextcloud user from a group by specifying the user ID and group ID. Use this to revoke group membership and access rights.

Instructions

Remove one account from a group.

DELETE /ocs/v2.php/cloud/users/{user_id}/groups

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>",
      "group_id": "<group_id>"
    },
    "name": "nextcloud_remove_user_from_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.
user_idYes
group_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not explain whether group-shared files remain accessible, whether shares are revoked, or what errors occur for non-members. The raw endpoint line is implementation trivia rather than behavioral context.

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?

The first sentence is tight and front-loaded, but the second sentence is a bare REST path that adds no decision-relevant information for an agent. Short overall, but one of two sentences is wasted.

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?

No output schema exists, so the description should explain the outcome (e.g. the state of membership after the call) and the role of the destructive-operation `confirm` flag. It does neither, leaving a destructive, multi-parameter mutation under-described despite rich annotations.

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 only 33% — just the `confirm` parameter is documented, and only in the schema, not the description. The description says nothing about user_id or group_id (format, whether it accepts display names or identifiers), so it fails to compensate for the coverage gap.

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 states a specific verb and resource: 'Remove one account from a group.' That is unambiguous and clearly the inverse of the sibling nextcloud_add_user_to_group, even though no sibling is named explicitly. It falls short of a 5 only because it does not call out the alternative tool by name.

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 guidance on when to use this versus alternatives (e.g. nextcloud_delete_group, nextcloud_disable_user), no statement of required admin privileges, and no note about what happens if the user is not a member. Usage is only inferable from the verb in the name.

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

Deploy Server

Other Tools