Skip to main content
Glama

n8n_manage_datatable

Destructive

Manage n8n data tables and rows: create, list, get, update, delete tables, plus insert, update, upsert, delete rows with filters, pagination, and dry run preview.

Instructions

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

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 name (rename only — schema is immutable after creation)
limitNoFor listTables/getRows: max results (1-100)
actionYesOperation to perform
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. Schema is immutable after creation via public API.
tableIdNoData table ID (required for all actions except createTable and listTables)
projectIdNoFor createTable: project ID to create the table in. If omitted, uses the default project.
returnDataNoFor updateRows/upsertRows/deleteRows: return affected rows (default: false)
returnTypeNoFor insertRows: what to return (default: count)
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description lists destructive actions (deleteTable, deleteRows) but adds no further behavioral context such as irreversibility, required permissions, or side effects.

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 concise sentences, the first stating purpose and the second listing actions. Efficient, though grouping actions by category (table vs row) could improve readability.

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?

With 14 parameters and no output schema, the description is somewhat complete given high schema coverage, but it lacks guidance on required parameters per action, error handling, or return value 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%, so the schema already documents all parameters. The description adds no parameter-level guidance beyond listing actions, which is already covered by the action parameter's enum.

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 clearly states it manages n8n data tables and rows, listing all 10 possible actions. This verb+resource specification is specific and distinguishes the tool from its workflow-focused siblings.

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?

No explicit when-to-use or when-not-to-use guidance is provided, but the unique domain (data tables) compared to siblings implies appropriate contexts. The description lacks alternatives or exclusions.

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

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