Skip to main content
Glama

What performed on the user's own LinkedIn

flypost_get_post_analytics
Read-only

The user's own published LinkedIn posts with LinkedIn's native numbers (impressions, reach, reactions, comments, saves, engagement rate), ranked, plus median impressions per format. Covers every post on their profile, not just ones published through Flypost. Use it BEFORE pitching ideas: find which topics and formats actually earned reach, and model new ideas on those rather than on guesses. Read-only and unbilled.

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": "flypost_get_post_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPosts to return (default 15).
formatNoOnly one post format, e.g. image, carousel, text, article, infographic, single_image.
sort_byNoRanking for the returned posts. Default impressions.
project_idNoProject id; omit for the active project.
since_daysNoOnly posts published in the last N days. Omit for all tracked posts (up to ~12 months).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is structured data. The description adds real value beyond that with "unbilled" (a cost trait annotations cannot express) and the coverage scope of "every post on their profile." However, it says nothing about data freshness or whether figures can be stale — a meaningful omission given a dedicated refresh sibling exists.

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?

Front-loaded with what is returned, then the intent guidance, then the cost note — good ordering for an agent scanning for purpose first. Three sentences carry little waste, though "Read-only and unbilled" partly restates the readOnly annotation and could be trimmed to the cost claim alone.

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 carries the burden of describing returns and it does so adequately: metric names, per-format medians, and ranking. For a read-only query tool that is close to sufficient; the missing pieces are the staleness/refresh relationship and any note on empty results, which matter because a refresh sibling exists.

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% and every parameter (limit, format, sort_by, project_id, since_days) is documented inline including defaults and bounds. The description adds no syntax or behavioral detail about these filters — e.g. how format interacts with the per-format medians — so the baseline 3 is appropriate.

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?

The description names the resource precisely ("the user's own published LinkedIn posts") and enumerates the returned metrics, so an agent knows exactly what this yields. It also states a scope boundary against an unnamed alternative — "not just ones published through Flypost." The one gap is that it never distinguishes itself from the nearby flypost_refresh_post_analytics sibling, so an agent cannot tell from the text whether reading is enough or a refresh must come first.

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 concrete situational guidance: "Use it BEFORE pitching ideas" and explains why (model new ideas on proven reach rather than guesses). That is a clear context signal, but there are no exclusions and no alternative named for the case where the agent needs fresh data or wants a single post's numbers.

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.