Skip to main content
Glama

Refresh post analytics from LinkedIn

flypost_refresh_post_analytics

Pull fresh numbers from LinkedIn for the project's tracked posts (the Post Analytics page's refresh). Runs in the background for a few minutes; flypost_get_post_analytics shows each post's metrics_at, so you can tell which numbers are fresh. Use it before judging how a recent post did, not before every read.

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

Input Schema

NameRequiredDescriptionDefault
project_idNoProject id; omit for the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description adds genuinely non-obvious behavior: the call returns immediately while the fetch runs in the background for several minutes. It also explains how to detect staleness via metrics_at rather than implying the read is instantly updated. It does not cover failure handling or whether concurrent refreshes coalesce, which is the remaining gap for a background job.

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?

Three short sentences, front-loaded with the action, then the async consequence, then the gating advice. Every sentence carries distinct decision-relevant information with no restatement of 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?

No output schema exists, and the description compensates by routing the agent to flypost_get_post_analytics for results and freshness verification. For a single-optional-parameter, non-destructive refresh this is nearly complete; only error/failure behavior is unaddressed.

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 the single project_id parameter is fully documented in the schema, so the baseline is 3. The description adds nothing about the parameter (e.g., that omitting it targets the active project), so no credit above baseline.

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?

States a concrete verb and resource ("Pull fresh numbers from LinkedIn for the project's tracked posts") and disambiguates from the sibling by naming the read path (flypost_get_post_analytics) and the UI surface it corresponds to. An agent can tell this apart from a plain analytics read without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit positive trigger ("before judging how a recent post did") and an explicit negative one ("not before every read"), plus names the read alternative for the non-refresh case. When-to-use and when-not-to-use are both spelled out.

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.