Skip to main content
Glama

n8n_get_workflow

Retrieve a specific workflow from n8n by providing its unique ID, enabling users to access and manage automation processes.

Instructions

Get a specific workflow by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWorkflow ID

Implementation Reference

  • The handler function that performs the API call to retrieve a workflow by ID.
    async getWorkflow(id: string): Promise<any> {
      const response = await this.client.get(`/workflows/${id}`);
      return response.data;
    }
  • src/index.ts:64-70 (registration)
    The tool execution logic in the main request handler loop.
    case 'n8n_get_workflow': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.getWorkflow(args.id as string as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • The MCP tool registration definition including the input schema.
      name: 'n8n_get_workflow',
      description: 'Get a specific workflow by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Workflow ID' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

With no annotations, the description carries full burden of behavioral disclosure. 'Get' implies read-only but doesn't confirm safety, disclose error conditions (e.g., 404 behavior), payload size, or return structure. Minimal behavioral context provided.

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 7 words. Front-loaded with verb first. No redundancy or fluff. However, brevity comes at cost of completeness given lack of annotations.

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?

Given zero annotations and no output schema, description is insufficient. Fails to describe what workflow data is returned, authentication requirements, or how this relates to other workflow operations in the extensive sibling set.

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 'id' parameter described as 'Workflow ID'. Description doesn't add parameter syntax/semantics, but with full schema coverage, baseline 3 is appropriate—no compensation needed.

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?

Clear verb (Get) + resource (workflow) + scope (specific by ID). Distinguishes from sibling list_workflows by emphasizing 'specific' and 'by ID', though could clarify this retrieves the workflow definition/configuration object specifically.

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?

No explicit guidance on when to use versus n8n_list_workflows (when ID known vs. discovery) or error handling if ID doesn't exist. Assumes user knows when to fetch by ID.

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