Skip to main content
Glama

n8n_manage_credentials

Manage n8n credentials through actions to list, get, create, update, delete, and discover required fields with getSchema. Credential data values are never logged.

Instructions

Manage n8n credentials. Actions: list, get, create, update, delete, getSchema. Use getSchema to discover required fields before creating. For list, page beyond 100 results with cursor (from the previous response's nextCursor). NOTE: list/get need an n8n deployment whose public API permits credential reads — older n8n versions, restricted API keys, or instance settings can reject them, returning NOT_SUPPORTED (create, delete, getSchema — and update where the API version supports it — still work). SECURITY: credential data values are never logged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoCredential ID (required for get, update, delete)
dataNoCredential data fields - use getSchema to discover required fields (required for create, optional for update)
nameNoCredential name (required for create)
typeNoCredential type e.g. httpHeaderAuth, httpBasicAuth, oAuth2Api (required for create, getSchema)
limitNoFor list: max results per page (1-100, default 100). Ignored when includeUsage is true.
actionYesAction to perform
cursorNoFor list: pagination cursor from a previous response's nextCursor. Ignored when includeUsage is true.
includeUsageNoFor list/get: also return workflows that reference each credential (id, name, active). On list, triggers a full scan of all credential pages (up to 5000 credentials; ignores cursor/limit, no nextCursor returned). Slower on large instances. Default: false.
Behavior5/5

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

Annotations indicate mutations allowed (readOnlyHint false, destructiveHint false) and open world. Description adds critical behavioral context: security (values never logged), version-dependent availability of list/get (NOT_SUPPORTED), and that create/delete/getSchema still work. No annotation contradiction.

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?

Well-structured with clear paragraphs for actions, pagination, and security. Front-loaded with purpose. Could be slightly more concise but each sentence adds value.

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?

Covers all actions, pagination, security, and limitations. No output schema, but description explains return values cursor and includeUsage behavior. Complex tool with 8 params, so quite complete. Small gap: could mention error handling or response format more.

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

Parameters5/5

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

Schema coverage is 100% with good descriptions. The description adds further meaning: cursor usage (from previous response's nextCursor), includeUsage triggers full scan, and getSchema to discover required fields. These details enhance parameter understanding 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 'Manage n8n credentials' and lists all actions (list, get, create, update, delete, getSchema). It distinguishes from sibling tools which are workflow-centric, so the purpose is specific and unique.

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

Usage Guidelines4/5

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

Provides explicit guidance: use getSchema before create, pagination with cursor, and notes when list/get may fail (older n8n versions, restricted API keys). No alternative tools to compare against, but the guidance is clear for when to use each action.

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

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