vaultwarden_bulk_delete_memberBulk remove members from a Vaultwarden organization in one operation by supplying the organization ID. Use it to clean up access for multiple users at once instead of deleting each member individually.
Bulk remove members from the org
| 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 readOnlyHint=false, so the safety profile is covered. The description adds only the org scoping, and says nothing about whether member data is permanently removed, what happens to vaults/collections they owned, or whether admin privileges are required — all critical for a destructive bulk operation.
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 short sentence with no filler, but it is under-specified rather than concise; nothing is front-loaded because there is almost nothing to front-load.
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 four opaque parameters, no output schema, and no annotations beyond the destructive hint. The description should at minimum explain the member-selection input and any irreversible consequences; it does neither.
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 coverage is 0%: org_id, form, params, and json_body have no types or descriptions. 'From the org' hints that org_id scopes the operation, but nothing explains how the target members are specified (presumably json_body) — the most important parameter semantics for this tool are missing.
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 specific verb ('Bulk remove') and resource ('members from the org'), which is clear. However, it does not differentiate from nearby siblings like vaultwarden_bulk_revoke_members or vaultwarden_delete_member, so an agent cannot tell which one to pick from the description alone.
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 guidance on when to use this versus bulk_revoke_members, delete_member, or bulk_restore_members. No prerequisites, no consequences stated, no exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.