Skip to main content
Glama
czlonkowski

n8n-MCP

by czlonkowski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

n8n_manage_datatable

Destructive

Create, list, update, and delete n8n data tables, rows, and columns. Filter, sort, and search rows for precise data management.

Instructions

Manage n8n data tables, rows and columns. Actions: createTable, listTables, getTable, updateTable, deleteTable, getRows, insertRows, updateRows, upsertRows, deleteRows, addColumn, deleteColumn, renameColumn. The column actions run through n8n's own MCP server (N8N_MCP_ACCESS_TOKEN, n8n 2.34+) because the public API cannot change a table's columns after creation; everything else uses the public API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoFor insertRows: array of row objects. For updateRows/upsertRows: object with column values.
nameNoFor createTable: table name. For updateTable: new table name. For renameColumn: new column name.
limitNoFor listTables/getRows: max results (1-100)
actionYesOperation to perform. addColumn/deleteColumn/renameColumn need N8N_MCP_ACCESS_TOKEN.
columnNoFor addColumn: the column to add. Name must start with a letter, contain only letters, digits and underscores, and be at most 63 characters.
cursorNoFor listTables/getRows: pagination cursor
dryRunNoFor updateRows/upsertRows/deleteRows: preview without applying (default: false)
filterNoFor getRows/updateRows/upsertRows/deleteRows: {type?: "and"|"or", filters: [{columnName, condition, value}]}
searchNoFor getRows: text search across string columns
sortByNoFor getRows: "columnName:asc" or "columnName:desc"
columnsNoFor createTable (required, at least one): column definitions. Change columns later with addColumn/deleteColumn/renameColumn.
tableIdNoData table ID (required for all actions except createTable and listTables)
columnIdNoFor deleteColumn/renameColumn: ID of the column (from getTable).
projectIdNoFor createTable: project ID to create the table in. If omitted, uses the default project. For the column actions: the project owning the table - resolved automatically when the instance has exactly one accessible project, otherwise required (the error lists the candidates).
timeoutMsNoFor the column actions: client timeout in ms (5000-600000, default 30000).
returnDataNoFor updateRows/upsertRows/deleteRows: return affected rows (default: false)
returnTypeNoFor insertRows: what to return (default: count)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.77.0
    • changedInput schema / properties / action / description
      Previous value: -"Operation to perform"New value: +"Operation to perform. addColumn/deleteColumn/renameColumn need N8N_MCP_ACCESS_TOKEN."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "createTable",
-  "listTables",
-  "getTable",
-  "updateTable",
-  "deleteTable",
-  "getRows",
-  "insertRows",
-  "updateRows",
-  "upsertRows",
-  "deleteRows"
-]New value: +[
+  "createTable",
+  "listTables",
+  "getTable",
+  "updateTable",
+  "deleteTable",
+  "getRows",
+  "insertRows",
+  "updateRows",
+  "upsertRows",
+  "deleteRows",
+  "addColumn",
+  "deleteColumn",
+  "renameColumn"
+]
    • addedInput schema / properties / column
      Added value: +{
+  "description": "For addColumn: the column to add. Name must start with a letter, contain only letters, digits and underscores, and be at most 63 characters.",
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "string",
+        "number",
+        "boolean",
+        "date"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "type"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / columnId
      Added value: +{
+  "description": "For deleteColumn/renameColumn: ID of the column (from getTable).",
+  "type": "string"
+}
    • changedInput schema / properties / columns / description
      Previous value: -"For createTable (required, at least one): column definitions. Schema is immutable after creation via public API."New value: +"For createTable (required, at least one): column definitions. Change columns later with addColumn/deleteColumn/renameColumn."
    • changedInput schema / properties / name / description
      Previous value: -"For createTable: table name. For updateTable: new name (rename only — schema is immutable after creation)"New value: +"For createTable: table name. For updateTable: new table name. For renameColumn: new column name."
    • changedInput schema / properties / projectId / description
      Previous value: -"For createTable: project ID to create the table in. If omitted, uses the default project."New value: +"For createTable: project ID to create the table in. If omitted, uses the default project. For the column actions: the project owning the table - resolved automatically when the instance has exactly one accessible project, otherwise required (the error lists the candidates)."
    • addedInput schema / properties / timeoutMs
      Added value: +{
+  "description": "For the column actions: client timeout in ms (5000-600000, default 30000).",
+  "maximum": 600000,
+  "minimum": 5000,
+  "type": "integer"
+}
  2. Addedv2.66.2
  3. Removedv2.65.1
  4. Addedv2.56.0
  5. Removedv2.55.0
  6. Addedv2.48.3

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds meaningful behavioral context: the public API cannot change table columns after creation, so those operations are routed through n8n's own MCP server with a token and version requirement. This gives the agent useful constraints beyond the structured annotations.

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 compact and front-loaded: it states the scope, lists all actions, then explains the key API split. The action list is long but necessary for a multi-action tool, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-action, 17-parameter tool, the description is adequate at an overview level and the schema fills in parameter details. However, with no output schema, it does not explain return formats, error behavior, or broader usage boundaries, so the agent still has to infer several operational details.

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%, with every parameter already documented in the input schema. The description itself adds no parameter-level meaning beyond the schema, so the baseline of 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?

The description states the resource ('n8n data tables, rows and columns') and enumerates 13 concrete actions, so an agent can see this is a broad CRUD hub for data tables. 'Manage' is generic, but the action list and resource make the purpose clear and distinguish it from sibling tools like n8n_manage_folders or n8n_manage_credentials.

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 gives an important internal routing rule: column actions require N8N_MCP_ACCESS_TOKEN and n8n 2.34+, while all other actions use the public API. However, it does not explicitly state when to prefer this tool over alternatives or when not to use it, leaving usage mostly implicit in the tool's name and description.

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