get_story_analytics
Captured Instagram story insights for a date range: views, reach,
replies, shares, profile visits, follows, and navigation (taps forward/
back, exits, swipe-forward) per story, ranked by engagement rate. Each
story also has profile_activity (bio link taps, call, email, directions,
text, other, total) and bio_link_taps, null for stories captured before
this metric was collected.
Story metrics only exist on Instagram for ~24h, so this can only ever
return stories posted after capture was switched on for this workspace
— check `capture_started_at` in the result. There is no way to backfill
stories from before that point; Meta has already discarded them.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_story_analytics"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| since | No | ||
| until | No | ||
| workspace_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| 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. | |
| capture_started_at | No |