Skip to main content
Glama
nikolausm

n8n MCP Server

by nikolausm

get_workflow

Retrieve detailed information about a specific workflow by providing its unique ID.

Instructions

Get detailed information about a specific workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesThe ID of the workflow

Implementation Reference

  • Tool registration/definition for 'get_workflow' with name, description, and inputSchema requiring workflowId (string).
    {
      name: "get_workflow",
      description: "Get detailed information about a specific workflow",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "The ID of the workflow",
          },
        },
        required: ["workflowId"],
      },
  • Handler for the 'get_workflow' tool: parses args with WorkflowIdSchema and calls client.getWorkflow(workflowId).
    case "get_workflow": {
      const { workflowId } = WorkflowIdSchema.parse(args);
      return await client.getWorkflow(workflowId);
    }
  • Client method getWorkflow: HTTP GET to /api/v1/workflows/{id}, validates response with WorkflowSchema.
    async getWorkflow(id: string) {
      const response = await this.client.get(`/api/v1/workflows/${id}`);
      return WorkflowSchema.parse(response.data);
    }
  • Zod schema WorkflowIdSchema used to validate the workflowId input parameter.
    const WorkflowIdSchema = z.object({
      workflowId: z.string(),
    });
  • Zod schema WorkflowSchema used to validate the API response for a workflow.
    const WorkflowSchema = z.object({
      id: z.string(),
      name: z.string(),
      active: z.boolean(),
      createdAt: z.string(),
      updatedAt: z.string(),
      nodes: z.array(z.any()),
      connections: z.record(z.any()),
      settings: z.record(z.any()).optional(),
      staticData: z.any().optional(),
      tags: z.array(z.string()).optional(),
Behavior2/5

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

No annotations; description only says 'Get detailed information' without explaining read-only nature, auth needs, or what 'detailed' includes. Lacks behavioral context.

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?

Single concise sentence. No wasted words, but lacks structure like sections or bullet points. Appropriate for a simple tool.

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?

No output schema; description should clarify return value contents. It doesn't specify what 'detailed information' includes (e.g., status, triggers, steps). Incomplete for agent decision-making.

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?

100% schema coverage; description adds no extra meaning beyond parameter name 'workflowId' already in schema. Baseline 3 is appropriate.

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?

Description clearly states the tool retrieves detailed workflow info. Distinguishes from siblings like list_workflows by specifying 'specific workflow', but does not explicitly contrast with search_workflows or get_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?

No guidance on when to use vs alternatives. Does not mention prerequisites or context for retrieving workflow details.

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

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