PostRite

Get the organization's analytics summary

get_analytics_summary

Read-only

Fetch aggregated engagement for the organization's published posts in a period: metric totals, per-platform breakdown, and an engagement-gained-per-day series.

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

Input Schema

Name	Required	Description	Default
`days`	No	Period in days (7, 30, 90; default 30)
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.

Output Schema

Name	Required	Description
`days`	No	Period length in days
`series`	No	Engagement gained per day, not cumulative
`totals`	No	Metric totals; null means the metric is not exposed, not zero
`postCount`	No
`byPlatform`	No
`previousTotals`	No	Same-length window immediately before, for comparison

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds scope (org-level, published posts only, bounded period) and the aggregation shape, but says nothing about freshness/latency of the metrics, whether unpublished or deleted posts are excluded, or what happens with no data — and there is an output schema, so return-shape detail is partly redundant.

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 front-loaded sentence with a verb-resource framing followed by a colon-delimited list of what is returned; no hedging, no filler, and the period scoping appears before the payload details.

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 two-parameter read-only analytics tool with a full output schema, the description covers scope, subject, and time window adequately. The one real gap is disambiguation from the several other analytics/insights tools in the sibling list.

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%: 'days' already documents the 7/30/90 enum with a default of 30, and 'organizationId' already explains the multi-org requirement and points to list_organizations. The description's 'in a period' adds no syntax or nuance beyond that, so the baseline 3 applies.

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?

States a specific verb ('Fetch') and resource ('aggregated engagement for the organization's published posts') plus the three output components, so the agent knows exactly what comes back. It never names the adjacent analytics siblings (get_analytics_insights, get_post_analytics, get_account_insights), so the boundary between them is left implicit.

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 is only implied by the phrase 'organization's published posts in a period' — that tells the agent this is org-wide aggregation rather than per-post, but gives no explicit when-to-use or when-not-to-use rule, and no guidance on choosing it over get_analytics_insights or get_top_posts.

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

All PostRite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?