Skip to main content
Glama

get_analytics_summary

Read-onlyIdempotent

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

NameRequiredDescriptionDefault
daysNo
sinceNo
untilNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
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.
best_hoursYes
posts_by_dayYes
total_failedYes
posts_in_rangeYes
ai_caption_rateYes
ai_hashtag_rateYes
total_publishedYes
total_scheduledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds real value beyond them: the heatmap always uses full history and ignores the range, timezone is the workspace's own clock, mixed window params are rejected, and omission defaults to 30 days. The only gap is that it doesn't mention result size, pagination, or any rate-limit behavior for a 12-month aggregation.

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

Conciseness5/5

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

Front-loaded summary first, then a clearly delimited two-option window block with per-option rationale, then the rejection and default rules. Every clause carries decision-relevant information; nothing is restated from the schema or annotations.

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

Completeness4/5

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

For a four-parameter read-only analytics tool with an output schema already documenting return values, the description covers window semantics, defaults, timezone, and the one surprising behavior (full-history heatmap) thoroughly. It stops short only on response shape/size expectations, which the output schema largely absorbs.

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 full burden and largely does: it gives days an integer/relative meaning tied to local time, gives since/until an explicit 'YYYY-MM-DD' inclusive format and timezone, and explains their mutual exclusivity and defaults. workspace_id is never described beyond being required and being the entity whose timezone list_workspaces reveals, leaving one parameter semantically thin.

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 opening sentence names a specific resource (posting activity summary) and enumerates its exact outputs: published/scheduled/failed counts per format, AI caption/hashtag share, a 12-month cadence heatmap, and top weekday+hour slots. That content profile is clearly distinct from the engagement-oriented siblings (get_reel_analytics, get_story_analytics, get_account_analytics), so an agent can route correctly 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?

Explicitly frames the window selection as 'pick exactly one style per call', gives the use case for each (days for relative asks, since/until for a specific calendar window), states that mixing them is rejected, and defines the default when all three are omitted. This is textbook when-to-use guidance with a stated exclusion.

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