Skip to main content
Glama

n8n_manage_datatable

Destructive

Create, list, update, delete n8n data tables and manage rows via insert, update, upsert, and delete actions.

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 indicate destructiveHint: true and readOnlyHint: false, so the description adds some context (e.g., 'Schema is immutable after creation'). However, it does not elaborate on safety or side effects beyond what annotations provide.

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 concise (one sentence plus structured schema). It front-loads the list of actions. The schema is well-organized with clear per-parameter details. No unnecessary text.

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, high complexity, and no output schema, the description provides a minimal overview. It covers actions but lacks context on return values, error handling, or workflow. The schema fills many gaps, but the description alone is incomplete.

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 baseline is 3. The description groups actions with parameter usage (e.g., 'For createTable: table name'), adding marginal value but not deeply explaining parameter interactions or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Manage n8n data tables and rows' and lists 10 actions, which is clear enough but generic. It does not differentiate from sibling tools beyond the specific domain of data tables, but the sibling tools are mostly workflow/credential management, so differentiation is minimal.

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?

No explicit guidance on when to use this tool versus alternatives. It simply lists actions without context for selection. The description does not provide any usage boundaries or recommendations.

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