Skip to main content
Glama

n8n_executions

Destructive

Manage n8n workflow executions: list runs, get execution details or error data, and delete records by ID.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoExecution ID. Required for action=delete; for action=get, omitting it lists executions instead
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)
actionNoOperation: get=get execution details, list=list executions (default), delete=delete executionlist
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)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv2.79.0
    • addedInput schema / properties / action / default
      Added value: +"list"
    • changedInput schema / properties / action / description
      Previous value: -"Operation: get=get execution details, list=list executions, delete=delete execution"New value: +"Operation: get=get execution details, list=list executions (default), delete=delete execution"
    • changedInput schema / properties / id / description
      Previous value: -"Execution ID (required for action=get or action=delete)"New value: +"Execution ID. Required for action=delete; for action=get, omitting it lists executions instead"
    • removedInput schema / required
      Removed value: -[
      -  "action"
      -]
  2. Addedv2.66.2
  3. Removedv2.65.2
  4. Addedv2.56.0
  5. Removedv2.55.0
  6. Addedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate destructive behavior and non-read-only status. The description adds value by specifying that delete 'removes the execution record' and clarifying the get/list/delete semantics. It does not contradict annotations, though it could further explain consequences like irreversibility.

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 concise: two sentences front-load the core purpose and then give the primary action routing. Every sentence earns its place without redundancy or filler.

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 high schema coverage and the tool's moderate complexity, the description is largely complete. It could add a note about response shape or mention that the delete action is irreversible, but the schema supplies the major parameter details and the description covers action selection.

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?

All 16 parameters have thorough descriptions in the schema, including enum values and per-action meaning, so the baseline is 3. The tool description itself does not add parameter-level detail beyond the action mapping, which the schema already covers.

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 identifies the resource (workflow executions) and enumerates the supported operations: get details, list, and delete. It also maps each action to its purpose, making the tool's scope unambiguous and distinct from sibling workflow management tools.

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 gives explicit guidance on when to use each action, including the default action and the role of 'id'. It does not explicitly compare against sibling tools or state when not to use this tool, but the action-level routing is clear and actionable.

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

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