Skip to main content
Glama

List Folders

keychain_list_folders
Read-only

List personal Bitwarden folders to organize and access password vault items. Use search and limit parameters to filter results.

Instructions

List Bitwarden folders (personal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNo
limitNo

Implementation Reference

  • Implementation of the "list_folders" tool (the tool name in the code uses the prefix from toolPrefix, resulting in "keychain_list_folders" assuming toolPrefix="keychain").
    registerTool(
      `${deps.toolPrefix}.list_folders`,
      {
        title: 'List Folders',
        description: 'List Bitwarden folders (personal).',
        annotations: { readOnlyHint: true },
        inputSchema: {
          search: z.string().optional(),
          limit: z.number().int().min(1).max(500).optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const folders = await sdk.listFolders(input);
        const results = folders
          .filter((x) => x && typeof x === 'object')
          .map((x) => {
            const rec = x as Record<string, unknown>;
            return { id: rec.id, name: rec.name };
          });
        return {
          structuredContent: { results },
          content: [{ type: 'text', text: `Found ${results.length} folder(s).` }],
        };
      },
    );
Behavior3/5

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

The annotation 'readOnlyHint: true' already indicates this is a safe read operation. The description adds minimal behavioral context by specifying 'personal' folders, which hints at scope, but doesn't disclose other traits like pagination, error handling, or authentication needs. No contradiction with annotations exists.

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 extremely concise—a single, front-loaded sentence with no wasted words. It efficiently conveys the core purpose without unnecessary elaboration.

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 lack of output schema and low schema description coverage (0%), the description is incomplete. It doesn't explain return values, parameter usage, or behavioral details, making it inadequate for a tool with two parameters and no structured output documentation.

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?

With 0% schema description coverage for the two parameters ('search' and 'limit'), the description provides no information about their purpose, usage, or semantics. It doesn't compensate for the lack of schema documentation, leaving parameters undocumented.

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 ('List') and resource ('Bitwarden folders') with the qualifier '(personal)', making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'keychain_list_collections' or 'keychain_list_org_collections', which also list different types of resources.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'keychain_search_items' for filtered searches or clarify the scope of 'personal' folders in relation to organizational ones, leaving the agent without usage context.

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