Changes and migrations · stop 5 of 10

edit_row

Inserts, updates or deletes one row by its primary key.

Needs write modeTool sets: full

You might ask

“Change customer 88's plan to annual.”

Your assistant may call edit_row to answer.

How it works

Needs write mode. You give the table, the values and the primary key, and the server builds the parameterized SQL.
Supports dry_run with a before-and-after diff, like execute_sql.

Parameters

actionstringrequired: Operation to perform: "insert", "update", or "delete".
tablestringrequired: Target table as "schema.name".
dry_runboolean: If true, execute then roll back so no change persists. Default false.
include_diffboolean: When true (default when dry_run), capture before/after row snapshots for update/delete.
pkobject: Primary-key column name/value pairs identifying the row. Required for update/delete.
valuesobject: Column name/value pairs to insert or update. Required for insert/update.

What your assistant reads

The description nexql-mcp sends with the tool. It's how the assistant decides when to use it.

Structured insert, update, or delete by primary key. The server builds parameterized SQL — pass table (schema.name), action, values, and pk for update/delete.