Skip to main content
Glama
Shravan1610

n8n MCP Server

by Shravan1610
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

n8n_pull_source_control

Pull changes from source control to update n8n workflows and configurations in your instance.

Instructions

Pull changes from source control

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/n8n-client.ts:281-284 (handler)
    The actual implementation of the tool, calling the n8n API endpoint /source-control/pull.
    async pullSourceControl(): Promise<any> {
  const response = await this.client.post('/source-control/pull');
  return response.data;
}
  • src/index.ts:404-409 (registration)
    Registration of the tool handler within the tool execution switch block.
    case 'n8n_pull_source_control': {
  const result = await n8nClient.pullSourceControl();
  return {
    content: [{ type: 'text', text: formatResponse(result) }],
  };
}
  • src/index.ts:913-920 (schema)
    Schema definition for the n8n_pull_source_control tool.
    {
  name: 'n8n_pull_source_control',
  description: 'Pull changes from source control',
  inputSchema: {
    type: 'object',
    properties: {},
  },
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavior, yet it only states the action without explaining consequences. It does not clarify whether this overwrites local workflow changes, handles merge conflicts, requires specific permissions, or affects the execution state of active workflows.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The four-word description is appropriately brief but fails to utilize the available space to convey critical behavioral context for a potentially destructive synchronization operation. While not verbose, the brevity results in under-specification rather than efficient information density.

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 that source control pull operations typically involve complex state management (conflicts, branch tracking, credential validation), the description is insufficient for safe invocation without additional external knowledge. The absence of an output schema and annotations compounds the need for descriptive completeness that is not met.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters in the input schema, the baseline score applies; the description appropriately does not fabricate parameter details. The description remains consistent with the empty schema structure.

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?

The description uses the specific verb 'Pull' and identifies 'source control' as the target resource, clearly indicating it retrieves changes from a version control system. While it conveys the basic operation, it does not explicitly differentiate from any hypothetical sibling source control tools (e.g., push, commit) or clarify that this operates on n8n's configured source control integration.

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?

The description provides no guidance on when to invoke this tool versus alternatives, nor does it mention prerequisites such as configured source control credentials or repository setup. There is no mention of error conditions, conflicts, or when the operation should be avoided.

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