Skip to main content
Glama

Publora

by com.publora
OverviewDiscussionsAdmin

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. Requires personal analytics access; Company accounts are unsupported.

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description adds real value: cached values may be returned, a numeric zero is valid while null/issue signal permission gaps, pending approval or transient failure, and it discloses the personal-analytics-only restriction and legacy `stats` field. Rich and consistent with the read-only annotation.

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 platform breakdown are front-loaded, and sentences are short and information-dense with no filler. It is on the long side for the amount of platform-by-platform detail, but essentially every sentence carries decision-relevant content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must convey return shape — it does, covering authoritative `results` rows keyed by platform+platformId+postedId, the retained legacy `stats`, cache behavior, and zero-vs-null semantics. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description goes further by tying `postedIds` to the `postedId` from get_post/list_posts and clarifying that for a thread only the root post qualifies — guidance the schema does not contain.

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') and immediately enumerates per-platform metric differences, so an agent can distinguish it from account-level siblings like profile_stats.

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?

Explicitly tells the agent to source IDs via get_post / list_posts and to pass the root post for threads, plus states the access prerequisite and the Company-account exclusion. It stops short of naming the sibling alternative (profile_stats) for account-level metrics, so it is clear context but not full routing.

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

All Publora 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