Skip to main content
Glama
Sign In
n8n MCP Server

n8n MCP Server

by verzth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update n8n Credential

n8n_update_credential
Idempotent

Update an existing n8n credential's display name or data by providing its ID. Merge new secrets into the credential's existing data.

Instructions

Update an existing credential's name or data.

Args:

  • id (string): Credential ID to update

  • name (string?): New display name

  • data (object?): Updated credential data/secrets (merged with existing)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "n8n_update_credential"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCredential ID
dataNoUpdated credential data/secrets
nameNoNew display name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds valuable context that 'data' is 'merged with existing', clarifying that the update is not a full replacement. This exceeds what annotations alone convey, though it does not cover auth or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is concise and front-loaded with the main action. However, the 'Args' section largely duplicates the input schema's parameter descriptions, adding redundancy. Still, the layout is clear and appropriate length.

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?

Given the tool's simplicity (3 parameters, no output schema), the description covers the essential behavior and the merge semantics. It is sufficiently complete for an AI to understand what the tool does and when to use it, though it omits return value details.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds the key nuance that the 'data' parameter is 'merged with existing', which is not fully captured by the schema's 'Updated credential data/secrets'. This provides semantic value beyond 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: 'Update an existing credential's name or data.' This uses a specific verb ('Update') and resource ('credential'), and distinguishes it from sibling tools like n8n_create_credential and n8n_delete_credential.

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

Usage Guidelines3/5

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

The description implies usage context (updating an existing credential) but provides no explicit alternatives or exclusions. It does not reference sibling tools like create or delete, leaving the when/why partly inferred from the tool name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools