Interaction history of a post
get_post_statsHow a post's views, forwards, replies and reactions (total and per-emoji) evolved over its life, as a sparse series of snapshots bucketed per hour or per day, oldest first — for view velocity and reaction drift. message_id comes from get_channel_posts. A post with no recorded snapshots answers an empty series.
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": {
"channel": "<channel>",
"message_id": "<message_id>"
},
"name": "get_post_stats"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | Only snapshots taken at or after this ISO 8601 timestamp | |
| until | No | Only snapshots taken before this ISO 8601 timestamp | |
| bucket | No | Series resolution: one snapshot per hour (1h) or day (1d) | 1h |
| channel | Yes | Channel slug (Telegram username, without the @) or numeric channel id | |
| message_id | Yes | Post id within the channel |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bucket | Yes | ||
| channel | Yes | ||
| chat_id | Yes | ||
| snapshots | Yes | Sparse, oldest first; empty for an untracked post | |
| message_id | Yes |