Skip to main content
Glama

n8n_executions

Destructive

Get execution details, list executions, or delete them. Choose from modes like summary, filtered, full, or error for tailored data retrieval.

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
actionYesOperation: get=get execution details, list=list executions, delete=delete execution
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
nodeNamesNoFor action=get with mode=filtered: filter to specific nodes by name
itemsLimitNoFor action=get with mode=filtered: items per node (0=structure, 2=default, -1=unlimited)
includeInputDataNoFor action=get: include input data in addition to output (default: false)
errorItemsLimitNoFor action=get with mode=error: sample items from upstream node (default: 2, max: 100)
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)
fetchWorkflowNoFor action=get with mode=error: fetch workflow for accurate upstream detection (default: true)
limitNoFor action=list: number of executions to return (1-100, default: 100)
cursorNoFor action=list: pagination cursor from previous response
workflowIdNoFor action=list: filter by workflow ID
projectIdNoFor action=list: filter by project ID (enterprise feature)
statusNoFor action=list: filter by execution status
includeDataNoFor action=list: include execution data (default: false)
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the 'delete' action, aligning with the destructive hint. However, it does not elaborate on what gets destroyed or any side effects beyond what annotations imply. This is acceptable but not enhanced.

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, front-loaded with the purpose. Every sentence is necessary and concise, providing clear instructions without verbosity.

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?

While the high schema coverage covers parameter details, the description omits return value information, pagination behavior, and potential side effects of deletion. Given the destructive nature and 16 parameters, the description could be more complete to guide the agent effectively.

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 coverage is 100%, so the description does not need to add much. The description only briefly references 'action' and 'id' without adding meaning beyond the schema. It meets the baseline but provides no extra semantic value.

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 tool's function: 'Manage workflow executions: get details, list, or delete.' It specifies three distinct actions, making the purpose unambiguous. Among sibling tools, no other tool manages executions, so differentiation is clear.

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 explicit guidance on when to use each action: 'Use action='get' with id ... action='list' ... action='delete'.' While it does not give contraindications or alternatives, the context is sufficiently clear given the lack of overlapping sibling tools.

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

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