Skip to main content
Glama

Create Logins

keychain_create_logins

Add multiple login credentials to your Bitwarden vault in one operation, supporting usernames, passwords, URIs, TOTP codes, notes, and attachments.

Instructions

Create multiple login items in a single call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
continueOnErrorNo

Implementation Reference

  • Implementation of the tool keychain_create_logins in registerTools.ts. Note: The tool is registered with the prefix defined in deps.toolPrefix.
    registerTool(
      `${deps.toolPrefix}.create_logins`,
      {
        title: 'Create Logins',
        description: 'Create multiple login items in a single call.',
        inputSchema: {
          items: z.array(
            z.object({
              name: z.string(),
              username: z.string().optional(),
              password: z.string().optional(),
              uris: z
                .array(
                  z.object({
                    uri: z.string(),
                    match: uriMatchInputSchema.optional(),
                  }),
                )
                .optional(),
              totp: z.string().optional(),
              notes: z.string().optional(),
              fields: z
                .array(
                  z.object({
                    name: z.string(),
                    value: z.string(),
                    hidden: z.boolean().optional(),
                  }),
                )
                .optional(),
              attachments: z
                .array(
                  z.object({
                    filename: z.string(),
                    contentBase64: z.string(),
                  }),
                )
                .optional(),
              favorite: z.boolean().optional(),
              organizationId: z.string().optional(),
              collectionIds: z.array(z.string()).optional(),
              folderId: z.string().optional(),
            }),
          ),
          continueOnError: z.boolean().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const results = await sdk.createLogins({
          items: input.items.map((it) => ({
            ...it,
            uris: normalizeUrisInput(it.uris),
          })),
          continueOnError: input.continueOnError,
        });
        return {
          structuredContent: { results },
          content: [
            { type: 'text', text: `Created ${results.length} login(s).` },
          ],
        };
      },
    );
Behavior1/5

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

With no annotations provided, the description carries full burden but fails to disclose any behavioral traits. It doesn't mention authentication requirements, error handling (despite 'continueOnError' in schema), rate limits, or what happens on success/failure. This is inadequate for a mutation tool.

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 waste. It's front-loaded with the core action and resource, making it easy to parse despite lacking detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex mutation tool with 2 parameters (one highly nested), 0% schema coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't address behavioral aspects, parameter meanings, or output expectations, leaving critical gaps for agent usage.

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 minimal value. It hints at 'multiple login items' (mapping to 'items' array) but doesn't explain parameter purposes, constraints, or relationships. The complex nested structure (e.g., 'uris', 'fields') remains 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 ('Create multiple login items') and resource ('login items'), which distinguishes it from the singular 'keychain_create_login' sibling. However, it doesn't specify what a 'login item' entails beyond the schema, making it slightly less specific than a perfect 5.

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 like 'keychain_create_login' (for single items) or other creation tools. It mentions 'in a single call' but doesn't explain trade-offs or prerequisites, leaving usage context unclear.

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