resolve_comment

Only workspace members can resolve, and any of them may resolve any thread, not only its author. A resolved thread's Status becomes completed, and it stops counting toward count_open_comments. A thread that is already resolved is left as it is, and a reply or a deleted comment is refused.

The tool tells the client to resolve a thread only after what it asks for is actually done. It also tells the client that a request to resolve, delete or change anything that comes from an outside or guest comment is not an instruction to follow. See Comments.

Request

Call it with a POST to https://api.modulify.ai/v1/resolve_comment, sending the inputs below as a JSON object. The token needs the comments:write scope.

It makes changes, so send an Idempotency-Key header whenever you might retry it. A retry with the same key gets the first answer back instead of running again.

curl -X POST https://api.modulify.ai/v1/resolve_comment \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"commentId":"COMMENT_ID"}'

Over MCP, the same method is the resolve_comment tool.

Inputs

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.