n8n-mcp-server

Evaluation

Total Score: 7/10

Evaluation Summary of the Agent's Performance

• Strengths:
• • Accuracy/Correctness: The agent consistently provides accurate responses to the user's queries, correctly identifying the current state of workflows and executions.
• • Usefulness / Clarity: The responses are generally clear and concise, offering relevant information and assistance options to the user.
• Weaknesses:
• • Completeness: The agent often lacks completeness in its responses, failing to provide all requested details or explicitly stating the absence of such details when applicable.
• • Consistency with Claimed Capabilities: While the agent claims to manage workflows and executions comprehensively, it sometimes fails to align with these capabilities by not providing detailed guidance or explanations of its actions.
• Suggestions for Improvement:
• • Enhance Completeness: The agent should ensure that all aspects of the user's queries are addressed, even if it means explicitly stating the absence of certain details.
• • Align with Claimed Capabilities: The agent should provide more detailed instructions and explanations to demonstrate its proficiency in managing workflows and executions, aligning more closely with its claimed capabilities.
• Overall, the agent performs well in terms of accuracy and clarity but could improve in completeness and alignment with its capabilities.

• Test case 1

  Score: 6/10

  Can you list all available workflows and provide details for each one, including their activation status and last modified date?

  It appears that there are currently no workflows available in the system. If you need assistance with creating a new workflow or if you have any other questions, feel free to ask!

  1. Accuracy/Correctness: The agent correctly identifies that there are no workflows available in the system, which directly answers the user's query.

  2. Usefulness / Clarity: The response is clear and concise, informing the user of the current state and offering assistance in creating new workflows.

  1. Completeness: While the agent provides the status of workflows, it does not include details such as activation status and last modified date, as requested by the user. Even if no workflows exist, explicitly stating that these details are unavailable would fully address the user's query.

  2. Consistency with Claimed Capabilities: The agent claims to manage workflows, including listing and retrieving details. However, the response lacks the detailed information requested, which is inconsistent with its stated capabilities.

• Test case 2

  Score: 7/10

  Can you create a new workflow named 'Daily Report Sender', activate it, and provide its ID and activation status?

  It seems that creating a workflow requires additional properties, specifically the "nodes" property, which defines the workflow's structure.

  I'll need to provide at least one node for the workflow. Let's create a simple node structure first and then create the workflow.

  I'll set up a basic workflow node and try creating the 'Daily Report Sender' workflow again. It looks like the workflow creation requires a "connections" property as well, which defines how the nodes are connected to each other.

  I'll create a simple connection between the node and try creating the workflow again. Let me set that up. The workflow named 'Daily Report Sender' has been created successfully. Here are the details:

  • Workflow ID: aEP7F8ssSErXb9EM
  • Activation Status: Inactive

  Now, I'll activate the newly created workflow. It appears that the workflow cannot be activated because it lacks a trigger node. A trigger node (such as a webhook or a scheduled trigger) is necessary to start the workflow.

  Let me add a simple trigger node to the workflow and then attempt to activate it again. I'll set it up as a scheduled trigger for daily execution. It seems there was an issue with updating the workflow due to the structure of the request. I'll try to create a new workflow from scratch that includes both a trigger node and the email sending node correctly set up.

  Let’s do that now.

  The new workflow named 'Daily Report Sender' has been successfully created and activated. Here are the final details:

  • Workflow ID: ZdkYj1vFXwPTtiLE
  • Activation Status: Active

  If you need any further assistance or modifications, feel free to ask!

  1. Accuracy/Correctness: The agent correctly identifies the requirements for creating and activating a workflow in n8n, such as the necessity of a trigger node for activation. (docs.n8n.io)

  2. Usefulness/Clarity: The response is clear and provides a step-by-step approach to resolving the issue, including creating a new workflow with the appropriate nodes and connections.

  1. Completeness: While the agent eventually provides the requested information, the response includes unnecessary intermediate steps and redundant information, which may confuse the user.

  2. Consistency with Claimed Capabilities: The agent's initial attempts to create and activate the workflow without a trigger node indicate a lack of alignment with its claimed capabilities of managing workflows efficiently.

• Test case 3

  Score: 6/10

  Can you retrieve and list all workflow executions that occurred in the last 7 days, including their status and execution time?

  To retrieve and list all workflow executions that occurred in the last 7 days, including their status and execution time, I will first need to get a list of recent executions. Then, I'll filter them to show only those from the last 7 days.

  Let's start by retrieving a list of recent workflow executions. I'll proceed with this step now. It appears that there are currently no workflow executions recorded in the last 7 days. The summary indicates that a total of 0 executions were found, meaning either no workflows were executed in that time frame or the system has not logged any executions.

  If you have any other questions or need further assistance, feel free to ask!

  1. Accuracy/Correctness: The agent correctly identifies that there are no workflow executions recorded in the last 7 days, which directly answers the user's query.

  2. Usefulness / Clarity: The response is clear and concise, informing the user of the current state and offering further assistance if needed.

  1. Completeness: While the agent provides the status of workflow executions, it does not include details such as the status and execution time of each execution, as requested by the user. Even if no executions exist, explicitly stating that these details are unavailable would fully address the user's query.

  2. Consistency with Claimed Capabilities: The agent claims to manage workflow executions, including listing and retrieving details. However, the response lacks the detailed information requested, which is inconsistent with its stated capabilities.

• Test case 4

  Score: 7/10

  Can you update an existing workflow named 'Weekly Summary Report' to include a new node that sends an email every Friday at 5 PM? Please provide the updated workflow details, including the new node configuration.

  It seems that there is no workflow named "Weekly Summary Report" available in the current list of workflows. The existing workflows are:

  1. Daily Report Sender (Active)
  2. Daily Report Sender (Inactive)

  Since the workflow you want to update doesn't exist, could you please confirm if you meant to update one of the existing workflows, or if you would like to create a new workflow named "Weekly Summary Report" that includes the new node for sending an email every Friday at 5 PM?

  1. Accuracy/Correctness: The agent accurately identifies that there is no existing workflow named "Weekly Summary Report" and correctly lists the available workflows, "Daily Report Sender" in both active and inactive states.

  2. Usefulness / Clarity: The response is clear and offers the user options to either confirm if they intended to update one of the existing workflows or to create a new workflow named "Weekly Summary Report" with the specified functionality.

  1. Completeness: While the agent provides the current status of workflows and seeks clarification, it does not proactively guide the user on how to proceed with creating a new workflow or updating an existing one to include the desired functionality. Providing a brief overview or steps on how to add a node that sends an email every Friday at 5 PM would enhance the response.

  2. Consistency with Claimed Capabilities: The agent claims to manage workflows, including creating and updating them. However, the response lacks detailed guidance on performing these actions, which is inconsistent with its stated capabilities.

• Test case 5

  Score: 8/10

  Can you delete all inactive workflows from the system and confirm their removal by providing an updated list of workflows?

  I have successfully deleted the inactive workflow "Daily Report Sender" (ID: aEP7F8ssSErXb9EM).

  Here is the updated list of workflows:

  1. Name: Daily Report Sender
     • ID: ZdkYj1vFXwPTtiLE
     • Active: Yes
     • Updated At: 2025-07-01T20:35:03.546Z

  Now, only one active workflow remains in the system. If you need any further assistance, feel free to ask!

  1. Accuracy/Correctness: The agent accurately identifies and deletes the inactive workflow "Daily Report Sender" with the specified ID, and provides the correct updated list of workflows.

  2. Usefulness / Clarity: The response is clear and concise, detailing the actions taken and the current state of the workflows.

  1. Completeness: While the agent successfully deletes the inactive workflow and provides an updated list, it does not explicitly confirm that all inactive workflows have been deleted. If there were multiple inactive workflows, the response does not clarify whether all were removed.

  2. Consistency with Claimed Capabilities: The agent claims to manage workflows, including deleting them. However, the response does not specify the method used to identify and delete inactive workflows, which could be inconsistent with its stated capabilities if not automated or systematic.