Skip to main content
Glama

How posts are doing

get_analytics
Read-onlyIdempotent

How a workspace's posts did in a period: views, reach, likes, comments, shares, saves, engagement (likes + comments + shares + saves) and engagement rate, clicks on Shager's tracked links, and followers — in total, compared with the previous period of the same length, day by day, by network, by account, and the top posts. Numbers come from each network's own API and refresh every few hours (often in a post's first day, then less). A post counts in the period it was published in, with its latest numbers. Totals add up what the networks report: Facebook views appear once Meta approves read_insights, LinkedIn shares numbers only for company Pages (impressions as views, unique impressions as reach, likes, comments, shares; followers) and none for personal profiles, and a TikTok account counts only after it is reconnected with the video-reading permission and only for its public videos (otherwise by_network.measured=false, coverage.notes) — only their link clicks count. get_post shows one post per account, with null for a number the network doesn't report. Google Business Profile locations have no post numbers; business_profiles gives each location's profile views, calls, website clicks and direction requests for the period, read live from Google. Use it to answer 'what worked this week', to pick the best time or format, or to report to a client. Filter with channel_ids or group_ids.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDate (2026-10-31, inclusive) or ISO datetime. Default: now
topNoHow many top posts to return (default 10)
fromNoDate (2026-10-01) or ISO datetime. Default: 30 days ago
group_idsNoOnly the accounts in these groups (from list_groups)
channel_idsNoOnly these accounts (from list_channels)
workspace_idYesWorkspace id from list_workspaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already establish safe/idempotent reads, yet the description adds substantial context beyond them: data refresh cadence ('every few hours'), attribution rule ('a post counts in the period it was published in, with its latest numbers'), and per-network prerequisites (Meta read_insights approval, LinkedIn company Pages only, TikTok reconnect plus public videos). It even discloses degraded-state fields (by_network.measured=false, coverage.notes), which is exactly the kind of behavior an agent needs to interpret surprising results.

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

Conciseness3/5

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

The metrics list is front-loaded, but the body is a long run-on sentence chaining freshness, attribution, and three network caveats, mixed with sibling routing and use cases. Most clauses are informative, but the dense parenthetical network detail is hard to scan and could be structured rather than strung together.

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?

With no output schema and a fairly complex response, the description does carry return-shape information: totals vs. previous period, day-by-day, by network, by account, and top posts, plus null handling for unreported numbers. It stops short of describing pagination or the top parameter's effect on the rest of the payload, but an agent could invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented with defaults and formats. The description only adds 'Filter with channel_ids or group_ids', which repeats the schema's intent without adding syntax, combination rules, or interaction with defaults. Baseline 3 applies when the schema does the heavy lifting.

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?

First sentence names the resource (a workspace's posts in a period) and enumerates the exact metric families returned: views, reach, likes, comments, shares, saves, engagement rate, link clicks, followers. It also distinguishes itself from get_post (single post) and business_profiles (Google Business Profile location metrics), so an agent can separate it from siblings 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 Guidelines4/5

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

Explicit use cases are given ('what worked this week', picking best time or format, client reporting) plus a direct pointer to get_post for single-post numbers and business_profiles for GBP locations. The only gap is that 'pick the best time' overlaps with the dedicated get_best_times sibling, which is never mentioned as the preferred alternative for that job.

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