n8n-free-mcp

List executions

list_executions

List workflow executions to debug and monitor your n8n workflows. Filter results by status or workflow ID for targeted analysis.

Instructions

List workflow executions. Useful for debugging: filter by status ('error', 'success', 'waiting') or by workflowId.

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": "list_executions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results (default 100)
`cursor`	No	Pagination cursor
`status`	No	Filter by status
`workflowId`	No	Filter by workflow

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 4, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as pagination behavior, rate limits, or response format. For a list operation without annotations, this is a significant gap.

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 two sentences with no wasted words. It front-loads the purpose and immediately provides useful filtering context.

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 tool has 4 parameters (all optional) and no output schema. The description does not explain the return format or pagination details, but it does mention the cursor parameter indirectly. For a list tool, more completeness would be beneficial.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters. The description adds value by emphasizing the debugging use case and listing the filter options (status, workflowId), but does not provide additional meaning beyond the schema for limit and cursor.

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 verb 'List' and the resource 'workflow executions', and adds context about filtering by status or workflowId. This distinguishes it from siblings like get_execution (single execution) or list_workflows.

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 indicates the tool is useful for debugging and specifies the available filters (status, workflowId). However, it does not explicitly mention when not to use it or compare to alternatives, though the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server