Skip to main content
Glama

Delete Org Collection

keychain_delete_org_collection

Remove an organization collection from a Bitwarden vault to manage access permissions and clean up unused data groups.

Instructions

Delete an organization collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYes
idYes

Implementation Reference

  • The handler for the 'delete_org_collection' tool, registered in 'src/tools/registerTools.ts'. It invokes 'sdk.deleteOrgCollection' after checking for read-only mode.
      `${deps.toolPrefix}.delete_org_collection`,
      {
        title: 'Delete Org Collection',
        description: 'Delete an organization collection.',
        inputSchema: {
          organizationId: z.string(),
          id: z.string(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        await sdk.deleteOrgCollection(input);
        return {
          structuredContent: { ok: true },
          content: [{ type: 'text', text: 'Deleted.' }],
        };
      },
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Delete' implying a destructive mutation, but lacks critical details: whether deletion is permanent or reversible, what permissions are required, if it affects child resources, or what happens on success/failure. This is inadequate for a destructive operation with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable. Every word earns its place, though this conciseness comes at the cost of completeness.

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?

For a destructive mutation tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't address behavioral risks, parameter meanings, expected outcomes, or error conditions. The agent lacks sufficient context to use this tool safely and effectively.

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 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'organizationId' and 'id' represent, their format, or where to obtain them. For a 2-parameter tool with no schema descriptions, this leaves the agent guessing about required inputs.

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 clearly states the action ('Delete') and target ('organization collection'), making the purpose immediately understandable. It distinguishes from siblings like 'keychain_delete_folder' or 'keychain_delete_item' by specifying the resource type. However, it doesn't explicitly contrast with 'keychain_delete_org_collection' alternatives (there are none) or explain what an 'organization collection' is beyond the 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing collection), exclusions (e.g., cannot delete if in use), or related tools like 'keychain_edit_org_collection' or 'keychain_list_org_collections'. The agent must infer usage from the tool name and sibling context alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/icoretech/warden-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server