Skip to main content
Glama

n8n_manage_datatable

Destructive

Manage n8n data tables and rows: create, list, update, delete tables; insert, update, upsert, delete, and query rows with filters, pagination, and sorting.

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 indicate destructiveHint: true. The description adds value by noting that schema is immutable after creation and mentioning dryRun, but lacks detail on other behaviors like idempotency or rate limits.

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, which is concise but flat. It lacks front-loaded summary or structured sub-sections for different operation groups, making it harder to parse quickly.

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

Completeness4/5

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

Given the complexity of 14 parameters across 10 actions, the description covers most necessary context such as action-specific parameter behavior. Missing output schema is compensated by description of returnType and returnData. Adequate but not exhaustive.

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?

With 100% schema coverage, baseline is 3. The description adds context beyond schema for several parameters (e.g., name clarifies usage per action, columns notes immutability), enhancing understanding.

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 clearly states 'Manage n8n data tables and rows' and lists 10 specific actions, making the tool's purpose evident. It distinguishes from sibling tools which focus on workflows and other operations.

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 on when to use this tool vs alternatives or which action to choose. The description merely lists actions without providing context on selection criteria 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/czlonkowski/n8n-mcp'

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