get_analytics_summary
Posting activity for a date range: how many reels/posts/carousels were published, scheduled, and failed; the share that used AI captions/ hashtags; a 12-month posting-cadence heatmap (always full history, ignores the range); and which weekday+hour combinations this account posts at most often.
Two ways to pick the window, pick exactly one style per call:
days: an integer count ending today, in the workspace's own local time — e.g. days=50 for "the last 50 days". Preferred for relative asks ("last N days", "this month so far") since it does the date math correctly against the account's own clock instead of you computing it.
since/until: explicit "YYYY-MM-DD" bounds (inclusive), in the workspace's own timezone (list_workspaces/get_posting_slots show it) — for a specific calendar window ("August 1 to August 15"). Passing days together with since/until is rejected as ambiguous. Omitting all three defaults to the last 30 days.
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>"
},
"name": "get_analytics_summary"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| since | No | ||
| until | No | ||
| workspace_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| range | Yes | The window a response was actually built for. Always echoed so a caller labels the numbers from what came back, not from request state — the 90-day clamp and the cache can both make those differ. | |
| best_hours | Yes | ||
| posts_by_day | Yes | ||
| total_failed | Yes | ||
| posts_in_range | Yes | ||
| ai_caption_rate | Yes | ||
| ai_hashtag_rate | Yes | ||
| total_published | Yes | ||
| total_scheduled | Yes |