Skip to main content
Glama

get_reel_analytics

Read-onlyIdempotent

Per-post performance for every reel/post/carousel published in a date range: views, reach, likes, comments, saves, shares, average watch time (reels only), caption, permalink, thumbnail, and whether it used AI-generated caption/hashtags. This is the tool for "how did my last N days of reels do" / "list my reel details" style questions — it returns one item per published post, newest first, not just a rollup.

Includes posts published natively on Instagram (not just ones scheduled
through reeldrop) — check each item's `source` field ("reeldrop" vs
"instagram"). Excludes stories — use get_story_analytics for those.

Feed posts and carousels also carry `profile_activity`: what people did
on the profile after seeing the post (bio_link_clicked, call, direction,
email, text, other, total), plus `bio_link_taps` as a shortcut. Sort by
`bio_link_taps` to answer "which post sent people to my link in bio".
Both are null for reels, because Instagram doesn't report this metric for
them, and for posts whose insights haven't been refreshed since it was added.

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_reel_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish a safe, idempotent read, so the extra context here is genuine surplus: results include natively-published Instagram posts beyond scheduled ones, the `source` field differentiates them, profile_activity is null for reels and for unrefreshed posts, and the window is computed in the workspace's own timezone. Ordering (newest first) and cardinality (one item per post, not a rollup) are also disclosed.

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 purpose and return contents, then segmented into a source/exclusions paragraph and a clearly bulleted parameter-mode section. It is on the long side and repeats the timezone point twice, but nearly every sentence removes an ambiguity an agent would otherwise hit.

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?

For a 4-parameter analytics read with an output schema, the description covers selection, exclusivity, defaults, timezone semantics, data-source caveats, and null conditions. Nothing an agent needs to call it correctly or interpret a null field is missing.

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

Parameters5/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 full burden and does: days is an integer count ending today in workspace-local time, since/until are inclusive YYYY-MM-DD bounds in the same timezone (with pointers to list_workspaces/get_posting_slots), the two styles are mutually exclusive, and the default is 30 days. This is meaning the schema alone does not convey.

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?

States a specific verb and resource (per-post performance for reels/posts/carousels in a date range) and enumerates the returned metrics, including the qualifier that watch time applies to reels only. It explicitly scopes itself against a named sibling ("Excludes stories — use get_story_analytics"), so an agent can distinguish it without opening a 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?

Gives concrete question patterns it answers ("how did my last N days of reels do", "which post sent people to my link in bio"), names the exclusion case with the alternative tool, and prescribes exactly when to use days vs since/until. It even states that mixing the two is rejected and that omitting all three defaults to 30 days, leaving nothing to inference.

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