Skip to Content
MCPToolsLinkedIn Post Engagers

LinkedIn Post Engagers

Give it a LinkedIn post URL, get back the people who reacted to it.

Tool
linkedin_post_engagers
Cost
0.3 credits
Category
LinkedIn Post Engagement
Required input
post_url
Returns
People who reacted to the post

What it does

  • Returns the people who reacted to a LinkedIn post — likes, celebrates and the rest.
  • Reacted, not commented. For the people who wrote a comment, use linkedin_post_commenters.
  • Results are paged. page_number runs 1 to 10 — each page is a separate call and a separate charge.
  • Reactions are a wider, shallower signal than comments. Most posts have several times more reactors than commenters, but a like says less than a sentence does.
  • Run both tools on the same post when you want full coverage of an audience.

This gives you people. It does not give you contact details — chain find_work_email for that.


Parameters

ParameterTypeRequiredNotes
post_urlstringYesFull LinkedIn post URL
page_numbernumberNo1–10, default 1

How to use it

Connect the MCP server

Follow the setup guide for your client. Browser sign-in, no API key.

Pull the reactors

Get the people who reacted to this LinkedIn post: <post_url>

Page through the rest

Now pull pages 2 to 10 of the same post. Stop early if a page comes back empty.

Add the commenters

Also pull the commenters on that post and merge the two lists, deduplicated by profile URL. Mark which people did both.

Filter, then enrich

Keep only Head of Sales, VP Sales and RevOps titles, then find their work emails. Do not guess email patterns. Report credits used.

Example prompts

Ask your clientWhat you get back
”Who reacted to this LinkedIn post?”Page 1 of reactors
”Pages 1 to 10 of reactors on this post”Ten calls, full reactor list
”Reactors plus commenters, deduplicated”The combined engaged audience
”Reactors on this post, then find their work emails”Chains find_work_email — 1 credit each

Best prompting practices

  • Say “reacted” or “liked”. “Engaged” is ambiguous and your client may route to linkedin_post_commenters instead.
  • Ask for pages explicitly. One call returns one page. “Pages 1 to 10” means ten calls and ten charges.
  • Rank commenters above reactors. When you merge the two lists, treat a comment as the stronger signal.
  • Filter before you enrich. A reactor list is long and mostly out of ICP. Cut it down before spending enrichment credits.
  • Pick posts on your topic. A post about the problem you solve produces a better list than a post about a brand.

Output

{ "engagers": [ { "name": "Jane Doe", "headline": "VP Revenue Operations", "profile_url": "https://linkedin.com/in/janedoe", "reaction": "LIKE" } ] }

Credits and limits

0.3 credits per call. One call returns one page, so 10 pages costs 3 credits. Maximum page number is 10. Run check_credits (free) before working through a list of posts.

Ten pages is the ceiling. A post with thousands of reactions will not give you all of them — take the pages you can and use the commenters as your priority tier.


ToolUse it instead when
linkedin_post_commentersYou want the people who wrote a comment — a stronger signal — 0.3 credits
linkedin_profile_reactionsYou want the inverse view — the posts one profile reacted to, returned as per-post engagement totals rather than the accounts that reacted — 0.2 credits
linkedin_profile_postsYou need a profile’s post URLs first — 0.3 credits
linkedin_page_postsYou need a company page’s post URLs first — 0.3 credits

Next steps


Keep learning

Two courses take these tools past the reference page — clustered by GTM job, then chained into workflows.