Skip to main content
Glama
Sign In
n8n MCP Server

n8n MCP Server

by verzth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List n8n Users

n8n_list_users
Read-onlyIdempotent

List all users in an n8n instance to manage access and permissions. Requires owner role; supports pagination with limit and cursor.

Instructions

List all users in the n8n instance. Requires owner role.

Args:

  • limit (number): Max results (1-250, default 20)

  • cursor (string?): Pagination cursor

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description goes beyond this by adding the owner role requirement, which is critical for authorization. It does not describe return format or pagination details, but with annotations covering side effects, this is adequate.

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 extremely concise, with a clear one-sentence purpose and a structured argument list. Every line provides useful information with no redundancy or filler.

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 (2 optional params), good annotations, and complete parameter semantics, the description is nearly complete. It lacks an explicit mention of the return value structure, but for a list operation with a cursor this is reasonably inferable. The owner role prerequisite adds important context.

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?

The schema has no property descriptions (0% coverage), so the description fully compensates by explaining 'limit' as 'Max results (1-250, default 20)' and 'cursor' as 'Pagination cursor'. This adds clear meaning to both parameters beyond the raw schema constraints.

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 'List all users in the n8n instance' with a specific verb and resource, and the scope is well-defined. This distinguishes it from sibling tools like n8n_list_workflows by naming the unique resource (users).

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 provides a clear prerequisite ('Requires owner role'), which is important context for when the tool can be used. It does not mention alternatives or exclusions, but the context is strong enough for an agent to know when to invoke this tool versus others.

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