Scrape post commenters
Direct LinkedIn read (bypasses our DB): live pull of who is commenting on ONE post right now. Returns transient commenter objects (member id, nickname, name, headline, comment text, posted_at, reactions_count) annotated with is_own and is_stored / linkedin_comment_sid. Target a tracked post by linkedin_tracked_post_sid XOR any post by URL / activity URN; the post does NOT need to be tracked. One wire page per call; page on with cursor. For the reconciled list with counts / groups / q, track the post and use linkedin-comments.search. Cost 2 credits.
Contract:
- MCP tool
scrape_linkedin_get_post_commenters, 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_commenters.
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.
128A tracked post (activity URN taken from the stored row). Exactly one of linkedin_tracked_post_sid / post.
18^ln_tp_A linkedin.com post URL OR an activity URN, auto-detected; a URL is resolved via get_activity_urn_by_url. The post does NOT need to be tracked. Exactly one of linkedin_tracked_post_sid / post.
512Default 50; one wire page per call.
1 <= x <= 100Opaque resume token from paging.next_cursor; null = first page.