Skip to main content
Glama

Get analytics per connected account

clipember_get_account_analytics
Read-onlyIdempotent

Views, likes, comments and posts published per connected social account and per network over the last 7, 30 or 90 days, a daily series and the best posts. Views are the latest snapshot of each post (taken 1h, 6h, 24h, 3d and 7d after it goes live), so new posts show no numbers for the first hours, and a TikTok upload has none until the person finishes it in TikTok. Bluesky has no view counts — its posts show likes, reposts (shares) and replies (comments); LinkedIn stats are not collected yet. Filter by platform or by connectionId (from clipember_list_platform_connections). History depth follows the plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clipember_get_account_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
daysNo
platformNo
connectionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "tiktok",
      -  "youtube_shorts",
      -  "instagram_reels",
      -  "bluesky",
      -  "facebook_reels",
      -  "threads",
      -  "linkedin"
      -]New value: +[
      +  "tiktok",
      +  "youtube_shorts",
      +  "instagram_reels",
      +  "bluesky",
      +  "facebook_reels",
      +  "threads",
      +  "linkedin",
      +  "pinterest"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark this read-only and idempotent, but the description goes well beyond them: views are lagging snapshots at fixed offsets, new posts read empty, TikTok uploads stay empty until finished in-app, Bluesky omits views and maps reposts/replies, LinkedIn is not collected at all. Plan-based history depth is also disclosed, which materially affects how results should be interpreted.

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?

The metric/scope statement is front-loaded, then the caveats follow in a compact sequence. Dense but wasteful-free; the parenthetical list of snapshot timings is slightly heavy but load-bearing for interpreting views.

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 read-only reporting tool with no output schema, the description adequately covers what comes back (metrics, daily series, best posts) and the platform-specific caveats. Remaining gaps are the `top` parameter's effect and any response shape/pagination detail, but neither blocks a correct call.

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?

With 0% schema description coverage, the description does the heavy lifting: it enumerates the days windows (7/30/90) and explains what connectionId is and where to get it. The `top` parameter (default 5, max 20) is never mentioned — only an unexplained 'best posts' phrase hints at it — and `platform` values are left to the enum, keeping this short of full coverage.

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

Purpose4/5

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

The description states a concrete set of metrics (views, likes, comments, posts published) at a concrete granularity (per connected account and per network) over concrete windows (7/30/90 days), plus the returned artifacts (daily series, best posts). It never names its closest sibling, clipember_get_autopilot_analytics, so the boundary between 'account analytics' and 'autopilot analytics' must be inferred.

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?

Filtering guidance is explicit — 'Filter by platform or by connectionId' — and it routes the agent to clipember_list_platform_connections to obtain a connectionId, which is a real prerequisite. What is missing is an exclusion clause: nothing says when to prefer the autopilot analytics sibling or what happens when neither filter is supplied.

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