Scrape post reactors
Direct LinkedIn read (bypasses our DB): live pull of who is reacting to ONE post right now, as transient reactor objects with normalized reaction_type (MAYBE → like + WARN), annotated with is_own and is_stored / linkedin_engagement_sid. Target by linkedin_tracked_post_sid XOR post URL / activity URN; tracking not required. One wire page per call; page on with cursor. For the reconciled list use linkedin-engagements.search on a tracked post. Cost 2 credits.
Contract:
- MCP tool
scrape_linkedin_get_post_reactors, registry packagemcp.linkedin/linkedin_scraping, mountlinkedin.scraping. - Operation
action, response envelopeaction. - Flags: creditable: the response carries a
creditsblock and the call can debit the team ledger.
Authorizations
Access token issued by gtm.service.id. Its access_identity claim carries team_sid, actor_sid and actor_type, and that team scope is authoritative.
Team scope for tokens that do not carry one. Ignored when the token already names a team.
Body
Request body of scrape_linkedin_get_post_reactors.
Executor account (ln_ac_...). OPTIONAL everywhere on this surface. Given: the call runs on that account ONLY; scraping bucket budget means charged 0, and a saturated or held bucket refuses 429 bucket_saturated (with retry_after), never a silent pool charge (§9.5 v5.2). To pay instead, omit this and pass use_credits: true.
18^ln_ac_Explicit pool opt-in (§9.5 v5.2). true with NO linkedin_account_sid: run on the platform pool and debit the method credit cost (reason infra_pool). Neither field: 422 executor_required. Both together: 422 (contradictory).
Ledger replay guard: a repeat call with the same (team, key) returns the stored outcome; no re-execution, no double charge. Recommended on every paid call. The KEY ALONE decides: the probe does not compare arguments, so reusing one key after changing the arguments hands back the FIRST result. On the twelve search verbs that matters twice over, because switching a call from filters to url (or back) under one key replays instead of running the new search. New search, new key.
128Exactly one of linkedin_tracked_post_sid / post.
18^ln_tp_Post URL OR activity URN, auto-detected; a URL is resolved via get_activity_urn_by_url. Exactly one of linkedin_tracked_post_sid / post.
512Default 50.
1 <= x <= 100Opaque resume token; null = first page.