Skip to main content
Glama

n8n_executions

Destructive

Get execution details, list executions, or delete execution records for n8n workflows. Retrieve full data, filtered node data, or error debugging information.

Instructions

Manage workflow executions: get details, list, or delete. Use action='get' with id for execution details, action='list' for listing executions, action='delete' to remove execution record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoExecution ID (required for action=get or action=delete)
modeNoFor action=get: preview=structure only, summary=2 items (default), filtered=custom, full=all data, error=optimized error debugging
limitNoFor action=list: number of executions to return (1-100, default: 100)
actionYesOperation: get=get execution details, list=list executions, delete=delete execution
cursorNoFor action=list: pagination cursor from previous response
statusNoFor action=list: filter by execution status
nodeNamesNoFor action=get with mode=filtered: filter to specific nodes by name
projectIdNoFor action=list: filter by project ID (enterprise feature)
itemsLimitNoFor action=get with mode=filtered: items per node (0=structure, 2=default, -1=unlimited)
workflowIdNoFor action=list: filter by workflow ID
includeDataNoFor action=list: include execution data (default: false)
fetchWorkflowNoFor action=get with mode=error: fetch workflow for accurate upstream detection (default: true)
errorItemsLimitNoFor action=get with mode=error: sample items from upstream node (default: 2, max: 100)
includeInputDataNoFor action=get: include input data in addition to output (default: false)
includeStackTraceNoFor action=get with mode=error: include full stack trace (default: false, shows truncated)
includeExecutionPathNoFor action=get with mode=error: include execution path leading to error (default: true)
Behavior4/5

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

Explains destructive behavior (delete) aligning with destructiveHint=true. Discloses various modes for 'get' (preview, summary, filtered, full, error) and other behavioral details beyond annotations, such as pagination with cursor.

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?

Two concise sentences front-load the purpose and then detail the actions. No wasted words; every sentence adds value.

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?

Adequate given 16 parameters and no output schema. Covers main actions and key parameters but lacks details on return format and advanced parameters like nodeNames and fetchWorkflow, which are only in schema descriptions.

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 parameters are already documented. Description adds high-level grouping by action but does not provide significant additional meaning beyond the schema.

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?

Description clearly states the tool manages executions with three operations (get, list, delete), using specific verbs and resources. It effectively distinguishes from sibling tools, none of which handle executions.

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?

Provides explicit guidance on when to use each action via 'action=' parameter. Clear context for each operation, though no exclusions or alternatives are mentioned, which is acceptable given no sibling tools overlap.

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

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