Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

get_post_analytics

Retrieve detailed per-platform analytics and engagement metrics for a specific post to measure performance and compare channel results.

Instructions

Get detailed per-platform analytics and engagement metrics for a specific post.

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": {
      "postId": "<postId>"
    },
    "name": "get_post_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post ID or requestId to fetch analytics for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden, yet it reveals almost nothing beyond the read nature implied by 'Get'. It does not mention permission or connection requirements, data freshness/lag, historical range limits, pagination, or behavior when the post ID is unknown or analytics are unavailable.

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?

One clean sentence with the resource and the scope front-loaded and no wasted wording. It is not padded, but it is also too thin to exploit its brevity for extra signal.

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

Completeness3/5

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

With one required parameter, no output schema, and no annotations, the definition is minimally viable: an agent knows what it retrieves and for which post. It falls short on the return shape (which platforms, which metrics, what time window) and on operational preconditions, which matter since no output schema exists to fill that gap.

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 coverage is 100% and the single postId parameter is fully documented, including the notable detail that it accepts either a post ID or a requestId. The description adds only the loose notion of 'a specific post', so the schema is doing the real work.

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 (Get) plus a distinct resource (per-platform analytics and engagement metrics) scoped to a single post. This is clearly separable from account-level tools like get_usage or get_follower_growth, though the description never names a sibling to sharpen the boundary.

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?

The phrase 'for a specific post' implies the scope but gives no explicit when-to-use guidance, no conditions that favor it over get_usage, get_follower_growth, or check_post_status, and no prerequisites such as requiring a connected account.

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