Skip to main content
Glama

get_post_analytics

Read-only

Numbers for ONE post you already know. Full metrics for one post, including how its reach/engagement built up over time (velocity) where available. Answers "how did my last post do?", "how did post 123 do?". Identify the post by post_id (from list_top_posts), by composition_id (the id in "Draft #123" and in list_drafts), or by latest: true for the most recent post, with a platform to narrow it to one network. For a LinkedIn post it also answers "what kinds of reactions did I get?" with the Like/Celebrate/Support/Love/Insightful/Funny split. Returns every per-post metric DemandBird tracks for that network, e.g. discussion rate, profile viewers, saves, sends and follows on LinkedIn.

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_post_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
latestNoFetch the most recent published post. Add `platform` to narrow it to one network.
post_idNoSocialPost id, e.g. from list_top_posts.
platformNoNarrow `latest` to one network.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
composition_idNoDemandBird post id: the number in "Draft #123", from list_drafts or save_draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a safe read-only operation. The description adds useful behavioral context beyond annotations: velocity over time where available, LinkedIn reaction breakdowns, and the fact that it returns every per-post metric tracked for that network.

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?

The description is front-loaded with the key scoping idea ('Numbers for ONE post') and remains readable. It includes some repetition between the first two sentences and illustrative examples, but the extra text mostly helps selection.

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 important work of explaining what is returned: all per-post metrics for that network, including velocity and LinkedIn reaction breakdowns. It is complete enough for invocation, though it does not discuss unavailable metrics or data freshness.

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 the schema already explains post_id, composition_id, latest, platform, and workspace. The description mostly restates those same identifier sources rather than adding substantially new parameter semantics, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: retrieving full analytics for exactly one known post. It explicitly scopes the tool to ONE post, which distinguishes it from sibling analytics/list tools such as get_analytics_summary and list_top_posts.

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?

It gives clear usage context with example questions and explains the three ways to identify a post: post_id, composition_id, or latest:true with platform. It does not explicitly state when to use aggregate alternatives like get_analytics_summary instead, so it falls short of full when/when-not guidance.

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.

Resources