Skip to main content
Glama

get_story_analytics

Read-onlyIdempotent

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

NameRequiredDescriptionDefault
daysNo
sinceNo
untilNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
itemsYes
rangeYesThe 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_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnly/idempotent/non-destructive annotations, it discloses a real data-availability constraint: story metrics live ~24h on Instagram, results only cover stories after `capture_started_at`, and backfill is impossible. It also flags that `bio_link_taps` is null for older stories and that ranking is by engagement rate — behavior an agent could not infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then a clearly bulleted window-selection section; every clause carries information, including the null-metric and capture caveats. It is dense and fairly long, but the structure keeps it scannable and nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value shape need not be spelled out, yet the description still previews the key fields. Combined with the capture-window limitation, timezone semantics, and window-selection rules, an agent has everything needed to call this correctly and to interpret empty or null results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the load, and it does: `days` is an integer count of days ending today in workspace local time, `since`/`until` are inclusive YYYY-MM-DD bounds in workspace timezone, the three are mutually exclusive, and the default is 30 days. The only gap is `workspace_id`, which is required but never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('captured Instagram story insights for a date range') and enumerates the returned dimensions (views, reach, replies, shares, profile visits, follows, navigation taps, profile_activity, bio_link_taps), ranked by engagement rate. That level of specificity lets an agent distinguish it from get_reel_analytics or get_account_analytics without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit selection rules: use `days` for relative asks ('last N days'), use `since`/`until` for explicit calendar windows, pass exactly one style, and passing both is rejected. It also states the default when all three are omitted (last 30 days) and points to list_workspaces/get_posting_slots for timezone, leaving little to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources