Feed, write
Record reply result
Record what a sent reply did, as one reading you took by hand. It is stored with source 'user': Sonket does not measure this and never infers it. Every field is optional, and a field you leave out is stored as not counted, which is not the same as zero. Readings are kept whole, so a correction is a new reading rather than an edit. It spends nothing.
MCP
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "record_reply_result",
"arguments": {
"project_id": "<uuid>",
"blip_id": "<uuid>"
}
}
}Input
The project. list_projects names them and marks the default.
The blip. list_blips names them.
Likes on your reply. Leave it out if you did not count it; that is stored as not counted, not as 0.
Replies to your reply. Leave it out if you did not count it; that is stored as not counted, not as 0.
Reposts of your reply. Leave it out if you did not count it; that is stored as not counted, not as 0.
Bookmarks on your reply. Leave it out if you did not count it; that is stored as not counted, not as 0.
Views or impressions on your reply. Leave it out if you did not count it; that is stored as not counted, not as 0.
True if the post's author replied to you, false if you looked and they had not. Leave it out when you did not look: that is not a false.
What else happened, which Sonket cannot see. One of: profile_visit, follow, dm, lead, customer. profile_visit is "Visited my profile", follow is "Followed me", dm is "Sent me a message", lead is "Became a lead", customer is "Became a customer". You reported this. Sonket cannot see it.
The permalink the reading came off. A link to a post on X, Bluesky or Hacker News.
Returns
The reading as stored and the item's figures folded over every reading so far, each one saying when it was read and where it came from.