Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

Pull from Source Control

n8n_source_control_pull

Pull changes from a remote Git repository into n8n workflows, with options to force pull and set variables after completion.

Instructions

Pull changes from the remote Git repository.

Args:

  • force (boolean): Force pull even with local changes (default: false)

  • variables (object, optional): Variables to set after pull

Returns: Pull result with affected files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoForce pull even with local changes
variablesNoVariables to set after pull

Implementation Reference

  • Handler implementation for the 'n8n_source_control_pull' tool, which performs an API call to /source-control/pull and formats the output.
      async (params: z.infer<typeof SourceControlPullSchema>) => {
        const result = await post<N8nSourceControlPullResult>('/source-control/pull', params);
        
        const files = result.pullResult?.files || [];
        const text = [
          `**Pull Complete**`,
          `- Status: ${result.statusCode}`,
          result.pullResult?.branch ? `- Branch: ${result.pullResult.branch}` : '',
          files.length ? `- Files Updated:\n${files.map(f => `  - ${f}`).join('\n')}` : '- No files changed'
        ].filter(Boolean).join('\n');
        
        return {
          content: [{ type: 'text', text }],
          structuredContent: result
        };
      }
    );
  • Registration of the 'n8n_source_control_pull' tool in the MCP server.
      server.registerTool(
        'n8n_source_control_pull',
        {
          title: 'Pull from Source Control',
          description: `Pull changes from the remote Git repository.
    
    Args:
      - force (boolean): Force pull even with local changes (default: false)
      - variables (object, optional): Variables to set after pull
    
    Returns:
      Pull result with affected files.`,
          inputSchema: SourceControlPullSchema,
          annotations: {
            readOnlyHint: false,
            destructiveHint: false,
            idempotentHint: false,
            openWorldHint: true
          }
        },
Behavior4/5

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

Annotations provide hints (readOnlyHint=false, destructiveHint=false, etc.), but the description adds valuable context: it mentions that pulling can affect files and includes a 'force' option for handling local changes, which clarifies operational behavior beyond the annotations. There's no contradiction with annotations, as 'pull' aligns with non-read-only and non-destructive hints.

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?

The description is well-structured and front-loaded with the core action, followed by brief parameter and return summaries. It avoids unnecessary details, but the parameter section slightly repeats schema info, making it less than perfectly concise. Overall, it's efficient and easy to scan.

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 tool's moderate complexity (Git operations with optional parameters), annotations cover safety aspects, and the description adds key behavioral context (e.g., force option, affected files). Without an output schema, the return statement is helpful but minimal. It's mostly complete but could benefit from more detail on error cases or integration with other source control tools.

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 description coverage is 100%, so the schema already fully documents the parameters. The description repeats some parameter info (e.g., 'force' and 'variables') but doesn't add significant meaning beyond what's in the schema, such as explaining how variables interact with the pull operation. This meets the baseline for high schema coverage.

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 states the specific action ('Pull changes') and resource ('from the remote Git repository'), making the purpose immediately understandable. It distinguishes itself from siblings like 'n8n_source_control_push' and 'n8n_source_control_status' by focusing on the pull operation, which is a distinct Git workflow step.

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

Usage Guidelines3/5

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

The description implies usage context through the mention of 'remote Git repository' and parameters like 'force', suggesting it's for syncing with source control. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., when to prefer 'n8n_source_control_status' first) or prerequisites like having a connected repository, leaving usage somewhat inferred rather than clearly defined.

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

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