Edit table rows with the AI assistant
Insert, update, and delete rows in an existing table without rewriting the whole table. Both the built-in assistant in ConvertSite and a connected AI tool through the ConvertSite MCP do this with the TableRows tool, shown as Change table rows among the MCP tools. To change the table's columns instead of its data, use Edit or Write as described at the end of this article.
Find the row you want to change
Updates and deletes need the row's ID, so the assistant reads the table first. One read returns at most 200 rows. In a larger table, the assistant can filter rows by the text in a column (matching is case-insensitive) or page through the table until it finds the row and its ID. You can simply ask for this, for example: “Find the row in the Orders table where Email matches the customer's address and give me its row ID.”
Insert, update, or delete rows
Open the assistant in your ConvertSite project, or use your connected Claude or Codex session. Editing table rows needs write access to your apps, which the MCP connection includes.
Describe the change and name the values. For example: “Add a row to the Orders table with PRODUCT set to Extended warranty and PRICE set to 49.”
For an update or a delete, let the assistant find the row ID first with a filtered read, then ask for the change: “Update that row so PRICE is 59” or “Delete that row.”
Check the result. The assistant reports how many rows it changed, and an insert returns the new row's ID so you can update or delete that row later.
These rules apply to every operation:
Values can use the column name or the column ID. An update changes only the cells you name; every other cell keeps its current value.
A value that is empty or missing clears the cell. On an insert, a column you leave out stays blank.
Dropdown columns need the option label exactly as it appears in the table. On a dropdown column with Multi select on, give a list of labels to select several options in one cell, for example ["Retail","Wholesale"], or one label for a single selection. Single-select columns keep using one label.
TableRows never touches the rows or cells your request does not name, so a row someone else adds while you edit stays in the table.
Batches and limits
One TableRows call carries up to 100 operations, applied in the order you asked for them. Ask for more than 100 and the assistant must split the work into several calls. Each call is all-or-nothing: if a single operation fails, nothing in that call is applied. The error message names the problem, such as the valid column names, the dropdown options to choose from, or how to find the missing row ID with a filtered read.
When to use Write or Edit instead
Use Edit or Write to change a table's structure: renaming, adding, or removing columns, or changing column types. Schema-only changes keep every existing row in place, so rows are safe while the columns change.
Write with a row list replaces the entire table content: every existing row that is not in your list is deleted. Because of that, Write refuses a full row replacement for a table with more than 200 rows. For anything else that changes the data in existing rows, use TableRows.
Asking the assistant to “rewrite the Orders table with these rows” triggers a full replacement through Write and deletes every row it did not list. Ask it to insert, update, or delete rows instead.
Assistant and MCP changes are saved as versions
The first time the assistant or an MCP session changes a table, ConvertSite saves the table as an Autosave before the change lands. When the assistant run or MCP session finishes, ConvertSite saves another version labeled with the source: AI edit, Claude Code edit, Codex edit, or MCP edit.
These versions appear in Version history in the table editor, so you can go back to the table exactly as it was before the AI touched it. See Restore a previous version of a table for how to open Version history and restore a version.