Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Delete n8n Credential

n8n_delete_credential
DestructiveIdempotent

Remove a credential from the n8n MCP Server to manage automation security. Note: This action may disrupt workflows that depend on the deleted credential.

Instructions

Delete a credential.

⚠️ WARNING: This will break any workflows using this credential!

Args:

  • id (string): Credential ID to delete

Returns: Confirmation of deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier of the resource

Implementation Reference

  • src/tools/credentials.ts:205-213 (handler)
    The handler implementation for n8n_delete_credential that performs a DELETE request to /credentials/{id}.
      async (params: z.infer<typeof IdParamSchema>) => {
    await del(`/credentials/${params.id}`);
    
    return {
      content: [{ type: 'text', text: `✅ Credential ${params.id} deleted successfully.` }],
      structuredContent: { deleted: true, id: params.id }
    };
  }
);
  • src/tools/credentials.ts:184-204 (registration)
    The MCP registration of n8n_delete_credential.
      server.registerTool(
    'n8n_delete_credential',
    {
      title: 'Delete n8n Credential',
      description: `Delete a credential.

⚠️ WARNING: This will break any workflows using this credential!

Args:
  - id (string): Credential ID to delete

Returns:
  Confirmation of deletion.`,
      inputSchema: IdParamSchema,
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: true,
        openWorldHint: false
      }
    },

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

The description adds crucial behavioral context beyond annotations: the warning about breaking workflows provides specific risk information that annotations (destructiveHint=true) only imply generally. However, it doesn't mention idempotent behavior (covered by idempotentHint=true) or other operational details like error conditions.

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 perfectly structured: warning first, then clear parameter documentation, then return information. Every sentence serves a distinct purpose with zero wasted words. The formatting with emoji and sections enhances readability.

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

Completeness4/5

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

For a destructive operation with good annotations, the description provides excellent risk context and clear parameter/return documentation. The only minor gap is lack of output details (no schema), but the 'Confirmation of deletion' statement provides adequate guidance for this simple 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 input schema already fully documents the single parameter. The description adds minimal value by restating 'Credential ID to delete' but doesn't provide additional context about ID format, sourcing, or validation beyond what's in the schema.

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 action ('Delete') and resource ('credential'), distinguishing it from sibling tools like 'n8n_get_credential' or 'n8n_update_credential'. It specifies the exact operation without ambiguity.

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 warning provides explicit guidance on when NOT to use this tool ('This will break any workflows using this credential!'), helping the agent avoid destructive actions when dependencies exist. It distinguishes this from safer alternatives like viewing or updating credentials.

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/DrBalls/n8n-mcp-server-v2'

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