Skip to main content
Glama

n8n_get_execution

Retrieve detailed information about a specific workflow execution in n8n by providing its execution ID.

Instructions

Get details of a specific execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesExecution ID

Implementation Reference

  • The handler logic in src/index.ts for the n8n_get_execution tool.
    case 'n8n_get_execution': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.getExecution(args.id as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • The implementation of the getExecution method in the n8n client, used by the tool handler.
    async getExecution(id: string): Promise<any> {
      const response = await this.client.get(`/executions/${id}`);
      return response.data;
    }
  • The tool registration schema for n8n_get_execution.
      name: 'n8n_get_execution',
      description: 'Get details of a specific execution',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Execution ID' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies read-only, it does not confirm safety, disclose error handling (e.g., invalid ID), or describe what execution details are returned.

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?

Extremely concise at six words with no redundancy. However, given the absence of annotations and output schema, it may be overly terse rather than efficiently informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Incomplete for a retrieval tool with no output schema: it fails to describe the structure or content of the returned execution details (status, timestamps, workflow ID, etc.) which agents need to handle the response.

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% with 'Execution ID' already describing the parameter. The description mentions 'specific execution' which loosely maps to the ID requirement but adds no format constraints, validation rules, or syntax details beyond the schema.

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

Purpose3/5

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

States the basic action (get details) and target (specific execution) clearly, but lacks specificity about what an 'execution' is in the n8n context and does not explicitly differentiate from sibling n8n_list_executions or n8n_retry_execution.

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?

Provides no guidance on when to use this versus n8n_list_executions (search/list) or n8n_retry_execution, nor does it mention prerequisites like having a valid execution ID from a prior workflow run.

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

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