Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get Active Webhooks

n8n_get_active_webhooks
Read-onlyIdempotent

Retrieve all active webhook endpoints and their linked workflows from an n8n automation server to monitor and manage incoming data triggers.

Instructions

Get a list of all active webhooks in the n8n instance.

Returns: List of active webhooks with their paths and associated workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/audit-utils.ts:164-179 (handler)
    The handler function for 'n8n_get_active_webhooks' that fetches active webhooks from the n8n API.
    async () => {
  const webhooks = await get<Array<{ webhookPath: string; method: string; workflowId: string; node: string }>>('/active-webhooks');
  
  const formatted = webhooks.map(wh => 
    `- **${wh.method}** \`${wh.webhookPath}\`\n  Workflow: ${wh.workflowId}, Node: ${wh.node}`
  ).join('\n\n');
  
  const text = webhooks.length > 0
    ? `**Active Webhooks (${webhooks.length})**\n\n${formatted}`
    : 'No active webhooks found.';
  
  return {
    content: [{ type: 'text', text }],
    structuredContent: { count: webhooks.length, webhooks }
  };
}
  • src/tools/audit-utils.ts:148-163 (registration)
    Registration of the 'n8n_get_active_webhooks' tool.
      server.registerTool(
    'n8n_get_active_webhooks',
    {
      title: 'Get Active Webhooks',
      description: `Get a list of all active webhooks in the n8n instance.

Returns:
  List of active webhooks with their paths and associated workflows.`,
      inputSchema: EmptySchema,
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false
      }
    },

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

Annotations provide strong behavioral hints: readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds value by specifying that it returns 'List of active webhooks with their paths and associated workflows,' which clarifies the output content beyond the annotations. However, it does not disclose additional traits like rate limits, authentication needs, or error conditions, leaving some behavioral aspects uncovered.

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 front-loaded with the core purpose in the first sentence, followed by a brief output specification. Both sentences are essential: the first defines the tool's action, and the second clarifies what is returned. There is no wasted verbiage or repetition, making it highly efficient and easy to parse.

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 (0 parameters, no output schema), the description is complete enough for an agent to understand its function. Annotations cover safety and idempotency, and the description adds output details. However, it lacks context on usage scenarios or error handling, which could be beneficial but is not strictly necessary for this low-complexity 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 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description does not need to compensate for missing parameter details, as there are none to explain. It appropriately focuses on the tool's action and output without redundant parameter information, aligning with the baseline for zero parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get a list of all active webhooks in the n8n instance.' It specifies the verb ('Get'), resource ('active webhooks'), and scope ('in the n8n instance'), which is specific and actionable. However, it does not explicitly differentiate from sibling tools like 'n8n_list_workflows' or 'n8n_get_workflow', which might also involve webhook-related data, though the focus on 'active webhooks' is distinct enough for clarity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, such as needing authentication or specific permissions, nor does it compare it to sibling tools like 'n8n_list_workflows' that might list workflows with webhooks. Without explicit when-to-use or when-not-to-use instructions, the agent must infer usage from the purpose alone.

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

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