Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

n8n: Get execution

n8n_get_execution
Read-only

Fetch details for a specific execution, including status, timing, and node outputs, to inspect workflow runs and diagnose failures.

Instructions

[UNIFIED] Get detailed information about a specific execution including status, timing, and node outputs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "execution_id": "<execution_id>"
    },
    "name": "n8n_get_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
execution_idYes
include_dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe read, so the bar is lower, and the description does add useful context by naming the returned fields (status, timing, node outputs). It is silent, though, on payload size risk, whether node outputs can be huge, and what include_data=false actually suppresses.

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?

A single front-loaded sentence that states purpose before details; nothing is padded. The bracketed "[UNIFIED]" token is the one piece that does not earn its space because its meaning is never defined.

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?

For a read tool with no output schema, the description does sketch the return contents, which is the right instinct. It still leaves the include_data/site semantics and the boundary with n8n_get_execution_data unresolved, so an agent can call it but cannot call it optimally.

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?

With three parameters and 0% schema description coverage, the description carries the burden and only partially meets it: "node outputs" hints that include_data governs output data retrieval, but the default of true and the cost of leaving it on are never explained. The required "site" parameter gets no semantics at all, which is a real gap given multi-site routing implications.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Get detailed information about a specific execution") and enumerates the payload contents: status, timing, and node outputs. However, the claimed "node outputs" overlaps with the sibling n8n_get_execution_data, and the unexplained "[UNIFIED]" prefix does nothing to separate the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus n8n_get_execution_data, n8n_wait_for_execution, or n8n_get_execution retries. Nothing tells the agent when include_data should be toggled or when this call is preferable to the data-specific sibling.

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

Deploy Server

Other Tools