Skip to main content
Glama

LinkedIn Post Reactions

linkedin_post_reactions

[Acquire · 1 credit/page] Fetch the people who reacted to a single LinkedIn post. Costs 1 credit per page of up to 100 reactions, walking up to max_pages pages (default 10), so at most max_pages credits; cached pages are free. The output's fetched / total_available / truncated fields say when the post had more reactions than were fetched. Engagers (with reaction kind) are persisted to the post_engagements graph so subsequent queries about who-engages-with-whom are SQL, not API calls.

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": {
      "post_url": "<post_url>"
    },
    "name": "linkedin_post_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoBypass the cache and re-fetch from LinkedIn (costs 1 credit per page). Default false: previously-fetched pages are returned free, with how long ago they were retrieved.
post_urlYesPublic LinkedIn post URL (e.g. https://www.linkedin.com/feed/update/urn:li:activity:1234)
max_pagesNoMax pages of up to 100 reactions to fetch (1-20, default 10). Each page costs 1 credit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / max_pages
      Added value: +{
      +  "description": "Max pages of up to 100 reactions to fetch (1-20, default 10). Each page costs 1 credit.",
      +  "maximum": 20,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / refresh / description
      Previous value: -"Bypass the cache and re-fetch from LinkedIn (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved."New value: +"Bypass the cache and re-fetch from LinkedIn (costs 1 credit per page). Default false: previously-fetched pages are returned free, with how long ago they were retrieved."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the credit pricing (1 per page of up to 100), the max_pages ceiling and default, that cached pages are free while refresh costs credits, that truncation is signaled via fetched/total_available/truncated, and — critically — that engagers are persisted to the post_engagements graph. That last point explains the readOnlyHint=false annotation and is exactly the side effect an agent needs to know about.

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?

Four sentences, front-loaded with a bracketed cost/action tag followed immediately by the purpose, then the cost model, then output/truncation semantics, then the persistence side effect. No sentence is filler and there is no redundant restatement of the tool name.

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

Completeness5/5

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

For a paginated, credit-metered, side-effecting fetch with no output schema, the description covers pricing, pagination limits, caching, truncation reporting, and the graph write. Nothing material to invoking it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters and baseline would be 3. The description adds derived meaning the schema does not: a cost ceiling expressed as 'at most max_pages credits' and the fact that cached pages are free, which frames the trade-off between refresh and max_pages.

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 specific verb and resource — 'Fetch the people who reacted to a single LinkedIn post' — and pins the scope to one post. That distinguishes it from sibling tools like linkedin_post_comments (comments, not reactions) and linkedin_profile_reactions (profile-level, not post-level) without needing to open 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 Guidelines3/5

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

The description implies when to use it (per-post reaction retrieval) and gives a cost model that helps an agent decide, but it never names an alternative tool or states an exclusion — e.g. when to prefer get_post_engagers_by_company or get_post_set_engagers, which plausibly overlap. Usage is inferable rather than guided.

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