Skip to main content
Glama
Sign In

PostFlow

by app.postflow
OverviewDiscussionsAdmin

Get posts analytics

get_posts_analytics
Read-only

Returns paginated performance metrics per published post in a group within a date range, plus sum and average across the range. Metric fields per row: views, reach, likes, replies, shares, saves, engagements, engagement_rate_impressions, engagement_rate_reach, video_views. Null means the network does not report the metric.

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": {
      "start": "<start>",
      "end": "<end>",
      "groupId": "<groupId>"
    },
    "name": "get_posts_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd of the range, ISO 8601 date, on or after start, at most 365 days later.
pageNoResult page, 25 rows per page.
startYesStart of the range, ISO 8601 date, not in the future.
groupIdYes
postTypesNoLimit to these post types. Omit for all.
socialAccountIdsNoLimit to these social accounts of the group. Omit for all accounts in the group.
showExternalPostsNoInclude posts published outside PostFlow. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description adds genuinely useful behavior: pagination, that aggregate sum/average rows are included alongside per-post rows, and crucially that null means the network does not report the metric. It does not mention permissions or rate limits, but the null semantics and aggregate-row disclosure go meaningfully beyond the annotations.

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?

A single dense sentence that front-loads scope, then aggregates, then the metric vocabulary. Every clause carries information; only the trailing metric enumeration feels slightly list-like, but it removes the need for an output schema.

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?

There is no output schema, so the description must describe the return payload, and it does: row granularity, aggregate rows, field names and null semantics. Gaps remain around ordering, timezone handling and how sum/average rows are identified in the response, but coverage is strong for a 7-parameter read tool.

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 86%, so the schema already explains start/end bounds, page size, postTypes, socialAccountIds and showExternalPosts. The description's metric-field list explains return values rather than parameters, so it adds no semantics to the inputs themselves. 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 and resource (returns per-post performance metrics for a group within a date range) and clarifies the aggregation behavior (plus sum and average). It implicitly separates itself from group-level siblings by scoping rows to individual published posts, though it never names an alternative such as get_post_metrics or get_groups_analytics.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no routing to the several overlapping analytics siblings (get_post_metrics, get_post_detail_metrics, get_groups_analytics). The agent must infer the choice purely from the wording of the name.

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

All PostFlow toolsInspect
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