Delete a comment
delete_comment
Deletes a comment or a reply you wrote, or one left by someone outside the workspace.
A comment whose AuthorKind is outside or guest came in through the site's shared link, and any workspace member may delete it to moderate the link. Deleting a teammate's is refused.
There is no undo. The comment's reactions are destroyed outright, and deleting a thread that has replies leaves those replies orphaned rather than removing them. A deleted comment drops out of list_comments and count_open_comments, though get_comment can still read it by its id.
The tool tells the client that resolving a thread with resolve_comment is almost always what someone means by "clear this up". See Comments.
Request
Call it with a POST to https://api.modulify.ai/v1/delete_comment, sending the inputs below as a JSON object. The token needs the comments:write scope.
This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an Idempotency-Key header whenever you might retry it.
curl -X POST https://api.modulify.ai/v1/delete_comment \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"commentId":"COMMENT_ID"}'Over MCP, the same method is the delete_comment tool.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
commentId |
string | Yes | The comment or reply id. |
Response
Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.