nc-mcp-server

delete_collective

DestructiveIdempotent

Permanently remove a collective from the trash, with an option to also delete its team and team folder. Requires it be in trash first; irreversible, all pages are erased.

Instructions

Permanently delete a collective from the trash.

The collective must be in the trash first (use trash_collective). This action is irreversible: all pages are permanently removed.

Args: collective_id: The numeric collective ID. delete_team: Also delete the team (circle) behind the collective, with every membership and anything shared with the team. Needs you to own the team; otherwise nothing is deleted. The team goes even if it existed before the collective. With false (default) it stays as an ordinary team. delete_team_folder: Deleting the team also deletes its team folder (Nextcloud 35+ with the Team folders app, which gives new collectives' teams one) and every file in it. With delete_team, the tool refuses if the team has a team folder unless this is true.

Returns: Confirmation message.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`delete_team`	No
`collective_id`	Yes
`delete_team_folder`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.9.0Oct 1, 2026

addedInput schema / properties / delete_team

Added value: +{
+  "default": false,
+  "title": "Delete Team",
+  "type": "boolean"
+}

addedInput schema / properties / delete_team_folder

Added value: +{
+  "default": false,
+  "title": "Delete Team Folder",
+  "type": "boolean"
+}

First observedv0.7.0Sep 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it specifies irreversibility, that all pages are removed, that the team and its folder contents are destroyed, that ownership is required or 'nothing is deleted', and that the tool refuses when a team folder exists unless delete_team_folder is set.

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?

Front-loaded with the core action and precondition before the Args section. The nested explanations of delete_team are dense but each clause conveys a genuinely distinct constraint; only mild trimming would be possible.

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?

An output schema exists, so the brief 'Returns: Confirmation message' is sufficient. For a destructive, multi-flag mutation with zero schema coverage, the description covers preconditions, side effects, failure modes, and ownership requirements.

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 description coverage is 0%, so the description carries the full burden and does: collective_id is a numeric ID, delete_team is explained with its side effects and ownership precondition, and delete_team_folder is tied back to delete_team with a version/refusal condition. This is meaning no schema alone could convey.

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 ('Permanently delete a collective from the trash') and immediately scopes it against the sibling operations trash_collective and restore_collective. An agent can distinguish this from any other delete_* tool without opening a schema.

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 an explicit precondition ('must be in the trash first (use trash_collective)'), names the setup tool, and warns the action is irreversible. It further explains when the optional flags apply and the ownership condition that governs them.

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

Deploy Server