Post a comment, reply, and like

When you finish any section on this page, a comment, reply, or like is in progress on a video that is already in the workspace. To add a URL first, paste a video URL or Find videos.

Post a comment

1. Open the video from Home.
2. If Generate is disabled, go back to Home, fill Product name, What it is, and Why it is better, then open the video again.
3. Type the parent comment, or click Generate and edit the draft until you would post it yourself.
4. Stay under the live max length shown in the composer.
5. Click Post.

Credits leave the workspace at submit. A kept line costs comment_credits from get_usage (25 today). You should see the thread move toward live. If you leave the video, open Threads.

Do not expect likes to go out in that same agent call. post_comment rejects a likes field. In the web app, Add likes on the same submit still waits for the comment to land.

Reply

Wait until the parent is live. If the composer still says the line is posting, wait.

1. Write the reply in the composer or on the live thread. Keep only lines you wrote or edited.
2. Stay under the live reply max length.
3. Send the reply.

A reply is another comment line. It costs the same comment_credits as the parent.

If you send the reply from MCP or REST, pass the video URL plus the parent owner username. Do not pass a YouTube lc URL, a cid, or a share-comment id. The fields are in Comment identity.

Like

If you want likes in the same web submit, click Add likes and set quantity at or above the minimum in the composer.

If you like after the comment is live:

• YouTube: use watch?v= plus lc= and the comment id.
• TikTok: use the video URL plus the comment owner username.

If quantity is below the live minimum, MCP and REST return QUANTITY. Rumora will not raise it. A like costs like_credits each (1 today). Trust get_usage for likeMin.

From an agent

Follow Comment then like for the curl. The MCP JSON is in Recommended workflow. The short order is:

1. get_usage
2. post_comment with video_url, text, and idempotency_key
3. get_status until identity is an object
4. like_comment or reply_to_comment with those identity fields