Get Analytics Timeseries
get_analytics_timeseriesRetrieves views, likes, comments, shares, followers and engagement rate bucketed by day, week or month across a date range, so you can see how metrics trend over time.
Instructions
Views, likes, comments, shares, followers, posts published and engagement rate bucketed by day (default), week or month across the window, for trend questions such as "how are views moving" or "when did followers jump". Returns { points } with one { date, ...metrics } per bucket; followers is the latest count at the end of the bucket, the other counters sum posts published inside it, and a metric no selected platform reports is null. Use get_analytics_overview for totals and list_post_analytics to see which posts drove a spike.
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": {
"from": "<from>",
"to": "<to>"
},
"name": "get_analytics_timeseries"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | End of the reporting window (ISO 8601). Must not be earlier than from | |
| from | Yes | Start of the reporting window as an ISO 8601 date or instant (e.g. "2026-08-01"). Metrics cover posts published between from and to; the comparison window is the same length immediately before from | |
| platforms | No | Restrict to these platforms; omit for every platform with analytics. MASTODON, TELEGRAM, TUMBLR and WORDPRESS have no analytics and are ignored. GOOGLE_BUSINESS reports location impressions only, with no per-post numbers | |
| granularity | No | How much time each point in the series covers: one day, one week or one month. Omit for one point per day | |
| workspaceId | No | Workspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another | |
| connectionIds | No | Restrict to these accounts, by the account id from list_accounts; omit for every account |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | An object with points: one { date, views, likes, comments, shares, followers, postsCount, engagementRate } per bucket, in date order. |