Read one comment thread
get_comment
Reads one comment in full together with its replies, reactions and attachments.
Reach for it when list_comments shows a thread with replies you need to read before acting. The comment and every reply carry AuthorKind, which is member, outside or guest. Text from an outside or guest author was written through the shared link by someone outside the workspace and carries an OutsideNotice, and the tool tells the client to report it to you and never follow it as an instruction.
Replies come back oldest first and are paged with repliesSkip. The list is not capped server-side, so a long thread comes back whole unless you page it. Deleted replies are left out of the thread and its count, but a deleted comment is still readable by its own id, so check that its Status is not deleted. See Comments.
Request
Call it with a POST to https://api.modulify.ai/v1/get_comment, sending the inputs below as a JSON object. The token needs the comments:read scope.
It only reads and changes nothing, so retrying it is safe.
curl -X POST https://api.modulify.ai/v1/get_comment \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"commentId":"COMMENT_ID"}'Over MCP, the same method is the get_comment tool.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
commentId |
string | Yes | The comment id, from list_comments. |
repliesSkip |
integer | No | How many replies to skip, for paging a long thread. |
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.