delete_rows

Deletes every row that matches the filters and returns how many were deleted. At least one filter is required.


Scope	`mcp:write`
Annotations	`destructiveHint: true`
Activity event	`delete_rows` with `table` and `count`

Deleted rows can’t be recovered. Run list_rows with the same filters first to check what matches.

Parameters

string

required

Project id from list_projects. You need write access.

string

required

Table name.

object[]

required

At least one condition. Rows must match all of them. See Filters.

Result

integer

The number of rows deleted from this table. Rows removed from other tables by cascade foreign keys aren’t counted.

Example

Arguments

{
  "projectId": "01k7m3x9q2v8d4h6n1r5t0w2yz",
  "table": "contacts",
  "filters": [
    { "col": "email", "op": "ilike", "value": "%@test.example" }
  ]
}

Result

{ "data": { "deleted": 4 } }

Foreign keys

When other tables reference the rows you delete, each foreign key’s onDelete rule applies:

Rule	Effect
`restrict` (default)	The whole delete is refused with `Referenced row does not exist, or the row is still referenced by another table`
`cascade`	Referencing rows in the other table are deleted too
`set null`	The referencing column in the other table is set to `NULL`

Errors

Code	When
`ACCESS_DENIED`	You don’t have write access, or the connection is read-only
`VALIDATION`	No filters, unknown table or column, an invalid filter, or a `restrict` foreign key blocks the delete

Notes

Deleting rows works even when the project has reached its storage limit, but it doesn’t reliably lower the measured size. See How storage is measured.

Overview

Read tools

Write tools

Destructive tools

Parameters

Result

Example

Foreign keys

Errors

Notes

​Parameters

​Result

​Example

​Foreign keys

​Errors

​Notes

Parameters

Result

Example

Foreign keys

Errors

Notes