Skip to main content
Glama

Delete Folder

keychain_delete_folder

Remove a personal Bitwarden folder from your vault to organize stored credentials and eliminate outdated or unnecessary categories.

Instructions

Delete a Bitwarden folder (personal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Tool definition and handler for keychain.delete_folder (registered as ${deps.toolPrefix}.delete_folder).
      `${deps.toolPrefix}.delete_folder`,
      {
        title: 'Delete Folder',
        description: 'Delete a Bitwarden folder (personal).',
        inputSchema: {
          id: z.string(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        await sdk.deleteFolder(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 but only states the action without behavioral details. It doesn't disclose if deletion is permanent, requires specific permissions, has side effects (e.g., affecting contained items), or rate limits. For a destructive operation, this lack of transparency is a significant gap.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every part earns its place by specifying the tool's focus.

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?

Given the tool's destructive nature, no annotations, no output schema, and 0% schema coverage, the description is incomplete. It lacks critical context like success/error responses, irreversible effects, or dependencies. For a delete operation, this minimal information is inadequate for safe and effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no parameter information beyond implying an 'id' is needed. It doesn't explain what the 'id' represents (e.g., folder UUID), how to obtain it, or format requirements. Baseline is 3 since the schema covers the single required parameter, but the description fails to compensate for the 0% coverage.

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 resource ('Bitwarden folder'), specifying it's for personal folders. It distinguishes from siblings like 'keychain_delete_item' or 'keychain_delete_org_collection' by focusing on folders, though it doesn't explicitly contrast with 'keychain_edit_folder' or 'keychain_get_folder'.

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. It doesn't mention prerequisites (e.g., needing an existing folder ID), exclusions (e.g., cannot delete system folders), or comparisons to siblings like 'keychain_delete_item' for broader deletions. The description is purely functional without contextual advice.

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