Skip to main content
Glama
Sign In
n8n MCP Server

n8n MCP Server

by verzth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List n8n Community Packages

n8n_list_community_packages
Read-onlyIdempotent

List all installed community node packages in an n8n instance to review and manage custom nodes.

Instructions

List all installed community node packages in the n8n instance.

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_community_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the specific scope of 'installed community node packages' but does not disclose additional behavioral details like return format or pagination. This is adequate but not rich.

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 a single sentence that is direct and front-loaded with the verb 'List'. Every word contributes to the meaning, with no redundant or unnecessary information, making it an ideal concise description.

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

Completeness5/5

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

For a tool with no parameters, no output schema, and strong annotations, the description fully covers the necessary context. It clearly states the operation and scope, and nothing essential is missing for an agent to correctly select and invoke the tool.

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?

The input schema has zero parameters, so there is no parameter semantics to explain. The baseline for zero-parameter tools is 4, and the description's phrase 'List all' is consistent with the lack of filters, requiring no additional parameter guidance.

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 uses the specific verb 'List' and clearly identifies the resource as 'all installed community node packages' in the n8n instance. This distinguishes it from sibling tools like n8n_install_community_package and other list tools, and matches the title exactly.

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 clear context: it lists installed community node packages, making it obvious when to use this tool. While it doesn't explicitly mention alternatives or exclusions, the clarity of the scope makes the usage unambiguous for a simple read-only operation.

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