vaultwarden_bulk_delete_organization_collectionsDeletes multiple organization collections by ID in a Vaultwarden/Bitwarden server, enabling bulk cleanup of collections within a specified organization.
Bulk delete collections by id
| Name | Required | Description | Default |
|---|---|---|---|
| form | No | ||
| org_id | Yes | ||
| params | No | ||
| json_body | No |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: no mention that deletion is irreversible, whether it requires elevated org permissions, or how many collections the bulk payload can contain.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler, but its brevity comes from omission rather than efficiency. There is no wasted text, yet almost nothing is said.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A destructive bulk mutation with an undocumented four-parameter schema, no output schema, and a large ambiguous sibling surface. The description leaves the critical question (how ids are supplied) unanswered, which is well short of complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across four parameters, so the description must compensate and does not. It refers to 'id' that does not exist as a named parameter and never explains whether the id list belongs in form, params, or json_body.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a recognizable verb+resource (bulk delete collections), which is enough to distinguish it from the single-item vaultwarden_delete_organization_collection. However, 'by id' is misleading: the schema exposes no 'id' parameter, only org_id plus opaque form/params/json_body containers, so an agent cannot tell where the ids actually go.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No statement of when to use this versus the single-collection delete sibling or vaultwarden_bulk_delete_groups, and no prerequisites such as admin/owner role or org scoping. The agent must infer everything from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.