Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

n8n: Execute workflow with data

n8n_execute_workflow_with_data
Destructive

Execute an n8n workflow with custom input data for webhook or manual triggers, enabling automations that need dynamic payloads.

Instructions

[UNIFIED] Execute workflow with custom input data. Useful for workflows with webhook or manual triggers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "workflow_id": "<workflow_id>",
      "data": "<data>"
    },
    "name": "n8n_execute_workflow_with_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
siteYes
workflow_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the agent knows this is a side-effecting write. The description adds nothing beyond that: it does not say the workflow actually runs and may take actions, whether data is validated, how long it may take, or whether repeated calls produce duplicate runs. The trigger-type clause is a faint hint at mechanics but not real behavioral disclosure.

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?

Two short sentences, front-loaded with the action, no filler sentences. The '[UNIFIED]' prefix and the hedged 'Useful for' phrasing are minor waste, but the definition is not padded.

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?

A destructive execute tool with a free-form nested object parameter, 0% schema coverage, and no output schema needs far more than two sentences. The agent cannot tell what to put in 'data', what 'site' means, or what an execution returns, and no output schema exists to fill that gap.

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

Parameters2/5

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

Schema description coverage is 0% across 3 required parameters, so the description must compensate and does not. 'Custom input data' hints at what 'data' carries, but says nothing about the expected shape of that arbitrary object, what 'site' identifies, or how 'data' maps onto the webhook/manual trigger payload.

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?

States a specific verb+resource: execute a workflow with custom input data. This distinguishes it from the bare n8n_execute_workflow sibling, though the '[UNIFIED]' tag is unexplained jargon that adds no information. The added clause about webhook/manual triggers narrows the purpose further.

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?

Implies when to use it (workflows with webhook or manual triggers) but never says when NOT to use it or names n8n_execute_workflow as the alternative for workflows without input data. The routing decision is left to inference from sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools