Skip to main content
Glama

Post statistics

post_stats
Read-only

Engagement counters for published Instagram, Threads, Mastodon or Bluesky posts. Instagram adds views, reach, shares and saves where supported. Threads returns lifetime views, likes (reactions), replies (comments), reposts, quotes and shares when available. Use the post's postedId from get_post / list_posts (for a thread, the root post only). Read authoritative results rows by platform + platformId + postedId; legacy stats is retained for older clients. Cached values may be returned. A numeric zero is valid; null and issue explain unavailable data, missing permission, pending app approval or a temporary failure. PERMISSION_REQUIRED means analytics permission is missing. When new analytics consent is enabled for this user, ask them to reconnect the same channel in Publora Channels (/dashboard/accounts) in the same environment and grant analytics permission; retry after reconnect. If new consent is disabled, an operator must enable it first; reconnect alone cannot add the permission. AUTH_REVOKED also requires reconnect. APP_REVIEW_PENDING means the feature is disabled or awaiting approval; reconnect does not fix it. Requires personal analytics access; Company accounts are unsupported.

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": {
      "platform": "<platform>",
      "platformId": "<platformId>",
      "postedIds": "<postedIds>"
    },
    "name": "post_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform of the posts
postedIdsYesPublished platform post IDs (`postedId`): Instagram or Threads media ID (not container ID), Bluesky AT-URI or Mastodon status ID. Max 50.
platformIdYesConnection ID from list_connections, e.g. 'threads-123', 'instagram-123', 'bluesky-did:plc:…' or 'mastodon-123' (prefix optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "mastodon",
      -  "bluesky"
      -]New value: +[
      +  "instagram",
      +  "threads",
      +  "mastodon",
      +  "bluesky"
      +]
    • changedInput schema / properties / platformId / description
      Previous value: -"Connection ID from list_connections, e.g. 'instagram-123', 'bluesky-did:plc:…' or 'mastodon-123' (prefix optional)"New value: +"Connection ID from list_connections, e.g. 'threads-123', 'instagram-123', 'bluesky-did:plc:…' or 'mastodon-123' (prefix optional)"
    • changedInput schema / properties / postedIds / description
      Previous value: -"Published platform post IDs (`postedId`): Instagram media ID (not container ID), Bluesky AT-URI or Mastodon status ID. Max 50."New value: +"Published platform post IDs (`postedId`): Instagram or Threads media ID (not container ID), Bluesky AT-URI or Mastodon status ID. Max 50."
  2. Changed3 schema fields changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "mastodon",
      -  "bluesky"
      -]New value: +[
      +  "instagram",
      +  "mastodon",
      +  "bluesky"
      +]
    • changedInput schema / properties / platformId / description
      Previous value: -"Connection ID from list_connections, e.g. 'bluesky-did:plc:…' or 'mastodon-123' (prefix optional)"New value: +"Connection ID from list_connections, e.g. 'instagram-123', 'bluesky-did:plc:…' or 'mastodon-123' (prefix optional)"
    • changedInput schema / properties / postedIds / description
      Previous value: -"Platform post IDs (`postedId`): Bluesky AT-URI, Mastodon status id. Max 50."New value: +"Published platform post IDs (`postedId`): Instagram media ID (not container ID), Bluesky AT-URI or Mastodon status ID. Max 50."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/destructive annotations by disclosing caching ('Cached values may be returned'), the zero-vs-null-vs-`issue` contract, the `results` vs legacy `stats` duality, and a full catalogue of failure modes (PERMISSION_REQUIRED, AUTH_REVOKED, APP_REVIEW_PENDING) with what each implies about remediation. The consent/reconnect operator escalation is exactly the kind of operational context annotations cannot express.

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?

Purpose and usage are front-loaded, then error semantics are grouped at the end, which is the right ordering. The platform-by-platform metric enumeration is dense but justified given there is no output schema. A few sentences on reconnect/consent repeat the same idea and could be tightened into one clause without losing meaning.

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 analytics fetch with no output schema, the definition covers the metric shape, caching, null semantics and every error path an agent is likely to hit. What's missing is minor: result ordering, whether partial per-ID failures return a row with `issue` or omit the ID entirely. Given the complexity of permission-gated analytics, this is close to complete.

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?

Schema coverage is 100%, so the schema already documents all three parameters, setting a baseline of 3. The description adds real meaning on top: the thread caveat that only the root post's ID counts, the identity triple (platform + platformId + postedId) needed for authoritative rows, and where postedId originates. It doesn't expand on the max-50 batch behavior beyond what the schema states.

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?

Opens with a specific verb+resource: 'Engagement counters for published Instagram, Threads, Mastodon or Bluesky posts.' It scopes platform coverage and implicitly separates itself from profile-level stats by naming the per-post `postedId` source. An agent can tell it fetches metrics for specific existing posts rather than listing or creating them.

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?

Gives a clear usage precondition and dependency: 'Use the post's `postedId` from get_post / list_posts (for a thread, the root post only).' It also states exclusions — personal analytics access required, Company accounts unsupported. It never names a sibling alternative (e.g. profile_stats for account-level metrics), so it stops short of full when-not routing.

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.