Skip to main content
Glama

n8n_delete_credential

DestructiveIdempotent

Permanently remove stored credentials from n8n workflows. Ensure dependent workflows are deactivated first to prevent workflow disruption.

Instructions

Remove stored credential. Cannot delete credentials currently used in active workflows. Deactivate dependent workflows first. Use with caution as this may break workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCredential ID to permanently delete

Implementation Reference

  • The actual handler that executes the n8n_delete_credential tool. Makes a DELETE request to the n8n API endpoint /api/v1/credentials/{id} with authentication headers.
    async deleteCredential(id: string) {
      return this.request(`${this.apiBase}/credentials/${id}`, { method: 'DELETE' });
    }
  • Schema definition for n8n_delete_credential tool. Defines the input parameters (id as required string), description, and annotations indicating this is a destructive operation.
      name: 'n8n_delete_credential',
      description: 'Remove stored credential. Cannot delete credentials currently used in active workflows. Deactivate dependent workflows first. Use with caution as this may break workflows.',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Credential ID to permanently delete' },
        },
        required: ['id'],
      },
      annotations: {
        title: 'Delete Credential',
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: true,
        openWorldHint: true,
      },
    },
  • src/server.ts:61-62 (registration)
    Routing logic in the handleToolCall function that maps the 'n8n_delete_credential' tool name to the client.deleteCredential method, passing args.id as the parameter.
    case 'n8n_delete_credential':
      return client.deleteCredential(args.id);
  • Type definition for N8nCredential objects, defining the structure of credential data including id, name, type, data, and timestamps.
    export interface N8nCredential {
      id: string;
      name: string;
      type: string;
      data?: any;
      createdAt: string;
      updatedAt: string;
    }
Behavior4/5

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

While annotations already indicate this is a destructive, non-readOnly operation, the description adds valuable behavioral context not covered by annotations: the constraint about active workflows, the need to deactivate workflows first, and the warning about potential workflow breakage. This goes beyond what annotations provide without contradicting them.

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 yet information-dense. Every sentence earns its place: the first states the purpose, the second provides critical constraints, the third gives prerequisites, and the fourth warns about consequences. No wasted words, and the most important information comes first.

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

Completeness5/5

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

For a destructive operation with comprehensive annotations (destructiveHint, idempotentHint, etc.), the description provides exactly what's needed: clear purpose, usage constraints, prerequisites, and warnings. The combination of annotations and description gives complete context for this tool's 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?

The schema has 100% description coverage with the parameter 'id' clearly documented as 'Credential ID to permanently delete'. The description doesn't add any additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the specific action ('Remove stored credential') and resource ('credential'), distinguishing it from sibling tools like n8n_create_credential or n8n_update_credential. It goes beyond just restating the name/title by specifying what type of object is being deleted.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when NOT to use this tool ('Cannot delete credentials currently used in active workflows') and what prerequisites are needed ('Deactivate dependent workflows first'). It also warns about consequences ('Use with caution as this may break workflows'), giving clear context for appropriate usage.

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/node2flow-th/n8n-management-mcp-community'

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