Reply to a comment
reply_to_commentPublishes a reply, as the account, to a comment on a post Shager published (YouTube, Facebook Pages, Instagram, X, LinkedIn company Pages, Bluesky, Mastodon and Threads). It is public at once and can't be unsent, so a person approves each reply in Shager first: the first call answers needs_confirmation with confirm_url, where your human sees the comment and your exact text; after they approve, make the same call again and it goes out. Up to 2,200 characters, within the network's own limit (Bluesky 300, Threads 500, Mastodon the server's). On X the reply is billed to the workspace's monthly X limit. delete_comment can remove it again except on Threads. (Not available in an unclaimed sandbox.)
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"workspace_id": "<workspace_id>",
"post_id": "<post_id>",
"channel_id": "<channel_id>",
"comment_id": "<comment_id>",
"text": "<text>"
},
"name": "reply_to_comment"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| post_id | Yes | ||
| channel_id | Yes | ||
| comment_id | Yes | ||
| workspace_id | Yes | Workspace id from list_workspaces | |
| confirmation_token | No | The confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url. |