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.
Preferred executor account (ln_ac_…). OPTIONAL everywhere on this surface: omitted → platform pool + credits (reason infra_pool); given with scraping-bucket budget → own account, charged 0; given but the bucket is saturated/held → automatic pool fallback (reason limit_fallback), never a 429 (§9.5).
18^ln_ac_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.
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.