Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Post Metrics

post_metrics
Read-onlyIdempotent

Retrieve metric snapshots for every target of a published post—views, reach, likes, comments, shares, saves, and clicks—oldest first; unsupported metrics are null.

Instructions

Metric snapshots (views, reach, likes, comments, shares, saves, clicks) of every target of a published post, oldest first. A metric the platform does not offer is null.

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

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post id (see post_list).
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral context beyond them: results are ordered oldest first, and metrics unavailable from the platform come back as null, which prevents the agent from misreading null as zero. It stops short of pagination or rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the first front-loads what is returned including the metric list and ordering, the second handles the null case. Every clause carries information; nothing is redundant with the title or 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?

With no output schema, the description must characterize the return value, and it does so at a high level (metric snapshots per target, oldest first, nulls allowed). The main remaining ambiguity is what a 'target' is (channel, platform, etc.) and whether the response is paginated, which a short clause could have resolved.

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 both parameters already carry descriptions pointing to post_list and organization_list for discovery. The description adds no additional meaning about postId or organizationId, so the baseline of 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?

Names the resource precisely ('metric snapshots ... of every target of a published post') and enumerates the metrics returned, so the agent knows exactly what data it gets. It does not differentiate itself from the sibling post_analytics, which is the one nearby tool that could plausibly serve the same need.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the way to retrieve per-target metrics for an already-published post, and the 'published post' qualifier hints at a precondition. There is no explicit when-to-use versus post_analytics or conversation_metrics, and no stated prerequisites or failure cases.

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

Deploy Server

Other Tools