Skip to main content
Glama

n8n_executions

Destructive

Get execution details, list executions with filters, or delete records. Supports pagination, status, and workflow filtering.

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 state destructiveHint=true, and the description includes a delete action, so consistency holds. However, the description adds no behavioral context beyond what annotations provide (e.g., auth needs, rate limits, side effects). With annotations carrying the burden, a score of 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys the tool's purpose and key usage patterns. It front-loads the verb and resource. While it is concise, it could be slightly more structured (e.g., bullet points) but remains effective.

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?

Given 16 parameters and no output schema, the description is minimal. It does not explain return values, pagination behavior for list, or error handling. Schema coverage is high, but for a complex tool, more contextual guidance would improve usability.

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 baseline is 3. The description briefly summarizes actions but does not add meaningful parameter semantics beyond what the input schema already provides (e.g., 'action' enum, 'id' requirement). No extra clarity on parameter values or constraints.

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 manages workflow executions with three specific actions (get, list, delete). It uses a specific verb 'manage' and resource 'executions', and distinguishes itself from sibling tools like n8n_get_workflow or n8n_delete_workflow which operate on workflows, not 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?

The description explicitly tells when to use each action (action='get' with id, action='list', action='delete'). It provides clear context for operation selection, though it does not explicitly mention when not to use the tool or name alternatives among siblings.

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