Skip to main content
Glama

n8n_manage_datatable

Destructive

Manage n8n data tables and rows: create, list, update, delete tables, and insert, update, upsert, delete rows with filtering, sorting, 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.
Behavior2/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 carries a low burden. However, it adds no context beyond the annotation—no mention of irreversibility, permission requirements, or side effects. The openWorldHint is also not explained.

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 very concise (one sentence plus a list) and front-loaded with the resource and intent. However, it could be better structured—grouping table vs. row actions 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?

For a tool with 14 parameters, nested objects, and no output schema, the description is too minimal. It fails to explain action interactions, return values, or provide usage examples, leaving the agent to rely solely on the schema.

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 baseline is 3. The description does not add any parameter-level meaning beyond the schema; it only lists action names. The schema already explains each parameter adequately.

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 identifies the resource ('n8n data tables and rows') and specifies the verb 'Manage' followed by an explicit list of 10 actions. This provides a specific and unambiguous purpose, and given the sibling tools are in different domains (workflows, credentials, etc.), the differentiation is inherent.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, context, or when not to use it. The agent must infer usage from the action list alone.

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