Skip to main content
Glama

n8n_manage_credentials

Manage n8n credentials by listing, getting, creating, updating, deleting, or using getSchema to discover required fields before creation.

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
actionYesAction to perform
idNoCredential ID (required for get, update, delete)
nameNoCredential name (required for create)
typeNoCredential type e.g. httpHeaderAuth, httpBasicAuth, oAuth2Api (required for create, getSchema)
dataNoCredential data fields - use getSchema to discover required fields (required for create, optional for update)
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.
cursorNoFor list: pagination cursor from a previous response's nextCursor. Ignored when includeUsage is true.
limitNoFor list: max results per page (1-100, default 100). Ignored when includeUsage is true.
Behavior5/5

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

The description adds significant context beyond annotations: it discloses that credential data is never logged, that list/get may fail on older/restricted n8n instances, and that includeUsage triggers a full scan ignoring pagination. These details are not in annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) and are consistent with 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 concise (6 sentences) while covering actions, usage guidance, edge cases, and a security note. It is front-loaded with the purpose and organized logically. No unnecessary words.

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

Completeness3/5

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

The description explains pagination and error handling, but it does not describe the return format for actions like get or create (e.g., credential object or success indication). Given the absence of an output schema, this omission reduces completeness for an 8-parameter tool with nested objects.

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?

All 8 parameters have schema descriptions (100% coverage). The description adds value by explaining cursor usage, includeUsage behavior, and getSchema role, which goes beyond the schema. However, the schema already covers parameter meaning well, so a slight premium 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 tool manages n8n credentials and enumerates all six supported actions (list, get, create, update, delete, getSchema). This is specific and distinct from sibling tools, which focus on workflows, nodes, or templates.

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?

The description advises using getSchema before creation, explains pagination with cursor for lists, and warns about potential NOT_SUPPORTED errors on restricted instances. It provides clear context but does not explicitly mention alternatives (which are unnecessary as this is the only credential tool).

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

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