Skip to main content
Glama

n8n_manage_datatable

Destructive

Perform CRUD operations on n8n data tables and rows, including creation, listing, updating, deletion, and row management with filtering and pagination.

Instructions

Manage n8n data tables and rows. Actions: createTable, listTables, getTable, updateTable, deleteTable, getRows, insertRows, updateRows, upsertRows, deleteRows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesOperation to perform
tableIdNoData table ID (required for all actions except createTable and listTables)
nameNoFor createTable: table name. For updateTable: new name (rename only — schema is immutable after creation)
columnsNoFor createTable (required, at least one): column definitions. Schema is immutable after creation via public API.
dataNoFor insertRows: array of row objects. For updateRows/upsertRows: object with column values.
filterNoFor getRows/updateRows/upsertRows/deleteRows: {type?: "and"|"or", filters: [{columnName, condition, value}]}
limitNoFor listTables/getRows: max results (1-100)
cursorNoFor listTables/getRows: pagination cursor
sortByNoFor getRows: "columnName:asc" or "columnName:desc"
searchNoFor getRows: text search across string columns
returnTypeNoFor insertRows: what to return (default: count)
returnDataNoFor updateRows/upsertRows/deleteRows: return affected rows (default: false)
dryRunNoFor updateRows/upsertRows/deleteRows: preview without applying (default: false)
projectIdNoFor createTable: project ID to create the table in. If omitted, uses the default project.
Behavior3/5

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

Annotations already mark destructiveHint as true, so the description's mention of deletion adds minimal value. It does note schema immutability after creation, which is a useful behavioral detail beyond annotations.

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 description is a single sentence listing actions. While concise, it lacks structure for a tool with 14 parameters; grouping or bullet points would improve readability.

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?

No output schema, and the description omits return value details, pagination behavior, or action chaining. For a high-complexity tool with 14 parameters and nested objects, this is insufficient.

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?

Schema coverage is 100%, allowing a baseline of 3. The description adds value by clarifying constraints (e.g., 'rename only' for name, 'required for all actions except createTable and listTables' for tableId, and immutability notes for columns).

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 explicitly states it manages n8n data tables and rows, listing all 10 actions. This clearly differentiates from sibling tools that focus on workflows, nodes, templates, or credentials.

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 lacks guidance on when to use this tool vs alternatives. It lists actions but provides no context on selection criteria, prerequisites, or exclusions. Sibling tools are not referenced.

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/czlonkowski/n8n-mcp'

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