Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Post Analytics

post_analytics
Read-onlyIdempotent

Retrieve publishing analytics for an organization over a chosen period, including totals, daily trends, top posts, and per-channel follower metrics to evaluate content performance.

Instructions

Publishing analytics for a period (default the last 30 days, at most a year): totals, a daily series, top posts and per-channel numbers with followers. A metric no channel offers is null.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "post_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the period. ISO 8601 date or date-time, e.g. 2026-09-01 or 2026-09-01T12:00:00Z.
fromNoStart of the period (posts published at or after it). ISO 8601 date or date-time, e.g. 2026-09-01 or 2026-09-01T12:00:00Z.
channelIdNoOnly this channel.
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds behavior the annotations cannot: a default lookback of 30 days, a hard one-year ceiling on the range, and the null convention ('A metric no channel offers is null'), which prevents an agent from misreading missing values as zero.

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?

One dense front-loaded sentence names the resource, the period rules and the exact payload, followed by a single short clause on null handling. Nothing is redundant and no sentence restates the tool name or title.

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, the description does the necessary work of enumerating what comes back (totals, daily series, top posts, per-channel figures with followers) plus the null convention, which is sufficient to call and interpret the tool. The remaining gap is the absence of any statement distinguishing this aggregate view from sibling metric tools.

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 from/to/channelId/organizationId are already documented, and the baseline is 3. The description does contribute the implicit default period and the maximum span, which constrain how from and to should be chosen, but it adds no format or interaction detail beyond the schema's own ISO 8601 examples.

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 specific verb+resource ('Publishing analytics for a period') and enumerates the return contents (totals, daily series, top posts, per-channel numbers with followers), which makes the tool's purpose concrete. It never names or contrasts with plausible siblings such as post_metrics or channel_statistics, so an agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage context is implied through the period semantics: default is the last 30 days and the range is capped at a year, which tells the agent what inputs are reasonable. There is no explicit when-to-use vs when-not guidance and no routing to a sibling for narrower metric or channel-specific queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools