Skip to main content
Glama

Create Login

keychain_create_login

Create a new login entry in your Bitwarden vault with username, password, URIs, TOTP, notes, and attachments for secure credential management.

Instructions

Create a login item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
usernameNo
passwordNo
urisNo
totpNo
notesNo
fieldsNo
attachmentsNo
favoriteNo
organizationIdNo
collectionIdsNo
folderIdNo

Implementation Reference

  • Handler for the 'create_login' tool in Bitwarden SDK.
      `${deps.toolPrefix}.create_login`,
      {
        title: 'Create Login',
        description: 'Create a login item.',
        inputSchema: {
          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(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const created = await sdk.createLogin({
          ...input,
          uris: normalizeUrisInput(input.uris),
        });
        return {
          structuredContent: { item: created },
          content: [{ type: 'text', text: 'Created.' }],
        };
      },
    );
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create a login item' implies a write/mutation operation, but provides no information about permissions required, whether this requires authentication, what happens on success/failure, rate limits, or any side effects. For a tool with 12 parameters that presumably creates sensitive authentication data, this lack of behavioral context is critically inadequate.

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 maximally concise at just three words. There's no wasted language or unnecessary elaboration. While this conciseness comes at the cost of informativeness, from a pure structure perspective, it's front-loaded and efficient with every word serving the core message.

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?

Given the complexity (12 parameters, no schema descriptions, no annotations, no output schema), this description is completely inadequate. For a tool that creates login items with numerous configuration options including URIs, TOTP, attachments, and organizational settings, the description provides none of the necessary context about what's being created, how it should be used, or what to expect as a result.

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

Parameters1/5

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

The schema description coverage is 0%, meaning none of the 12 parameters have descriptions in the schema. The tool description 'Create a login item' provides zero information about what any of these parameters mean, their purposes, or how they should be used. The description fails completely to compensate for the schema's lack of parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a login item' is a tautology that essentially restates the tool name 'keychain_create_login'. It doesn't specify what a 'login item' actually is or what resource it creates beyond the obvious. While it distinguishes this from sibling tools like 'keychain_create_card' or 'keychain_create_note' by specifying 'login', it lacks specificity about what constitutes a login item in this system.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this should be used instead of other creation tools (like 'keychain_create_logins' which appears similar), or any context about appropriate use cases. The agent receives zero usage guidance from this description.

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