Skip to main content
Glama

get_trial_reel_analytics

Read-onlyIdempotent

Performance of trial reels (published to non-followers first) in a date range: latest views/reach/likes/comments/shares/saves, engagement rate, views at 24h/72h after publish, the full sampled time series, and a heuristic "reach surge" — the largest single-interval reach jump, which is the best available hint (not a guarantee) that Instagram graduated the reel to followers' feeds.

reeldrop's own sampling, not Meta's — the Graph API has no trial-specific
insights and doesn't report graduation status.

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_trial_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.6/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description wisely spends its space on things annotations cannot convey: the data is reeldrop's own sampling rather than Meta's, the Graph API has no trial-specific insights or graduation status, and 'reach surge' is an explicit heuristic hint rather than a guarantee. It also discloses that ambiguous window combinations are rejected and what the default is — exactly the behavioral context an agent needs before calling.

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 payload, then the provenance caveat, then a bulleted window-selection block — a logical order with almost no filler. It runs longer than typical, but each paragraph carries distinct information (metrics, sampling caveat, window rules) rather than restating the schema.

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 values needn't be explained, yet the description still names the returned metrics precisely and flags their limitations. Together with timezone sourcing, default behavior, and the mutual-exclusion rule, an agent has everything needed to call this correctly on the first try.

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 coverage is 0%, so the description must carry all parameter meaning and it largely does: days is an integer count ending today in workspace-local time, since/until are inclusive 'YYYY-MM-DD' bounds in the workspace timezone, passing both styles is rejected, and omitting all defaults to 30 days. The only gap is workspace_id, whose semantics are left to the name, though list_workspaces/get_posting_slots are pointed to for discovering the timezone.

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?

Names a specific resource (trial reels, defined parenthetically as 'published to non-followers first') and enumerates exactly what is returned: views/reach/likes/comments/shares/saves, engagement rate, views at 24h/72h, sampled time series, and the 'reach surge' heuristic. That scope statement alone separates it from get_reel_analytics without opening either schema.

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

Usage Guidelines4/5

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

Gives explicit, actionable selection rules for the two window styles: days for relative asks ('last N days', 'this month so far') because it does date math against the account's clock, since/until for fixed calendar windows, mutual exclusion enforced, and a 30-day default when all three are omitted. It stops short of naming a sibling to use for non-trial reels, so tool-level routing is implied rather than stated.

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