Skip to main content
Glama

n8n_delete_credential

Remove a credential from n8n by specifying its ID to manage access and maintain security in workflow automation.

Instructions

Delete a credential

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCredential ID to delete

Implementation Reference

  • Implementation of the deleteCredential method which performs the actual API request to delete the credential.
    async deleteCredential(id: string): Promise<any> {
      const response = await this.client.delete(`/credentials/${id}`);
      return response.data;
    }
  • The tool call handler for n8n_delete_credential, responsible for parsing arguments and invoking the client method.
    case 'n8n_delete_credential': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.deleteCredential(args.id as string);
      return {
        content: [{ type: 'text', text: `Credential ${args.id as string} deleted successfully` }],
      };
    }
  • src/index.ts:626-636 (registration)
    Tool registration and input schema definition for n8n_delete_credential.
    {
      name: 'n8n_delete_credential',
      description: 'Delete a credential',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Credential ID to delete' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies destruction, the description omits critical safety details: whether deletion is permanent, impact on workflows using this credential, or required permissions. For a destructive operation, this 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately brief at three words, but suffers from under-specification rather than elegant conciseness. It front-loads the action but wastes the opportunity to add safety warnings or usage constraints that would justify its existence beyond the tool name.

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?

As a destructive operation with no output schema and no annotations, the description should disclose return values (success/failure indicators) and side effects. The minimal description fails to provide sufficient safety context for an irreversible deletion operation.

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?

With 100% schema description coverage (the 'id' parameter is fully documented as 'Credential ID to delete'), the baseline score is 3. The description text itself adds no parameter-specific semantics beyond what the schema already provides, but does not need to compensate given complete schema coverage.

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 'Delete a credential' is essentially a tautology that restates the tool name (n8n_delete_credential converted to sentence case). While the verb and resource are clear, it fails to distinguish from sibling deletion tools (delete_workflow, delete_user, etc.) or explain what constitutes a credential in the n8n context.

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 provided on when to use this tool versus alternatives like transfer_credential, nor are prerequisites mentioned (e.g., verifying the credential is not in use by workflows). The description lacks any when-to-use or when-not-to-use 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/Shravan1610/n8n-mcp-server'

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