Scrape posts by URL
Run ONE page of a LinkedIn content-search URL: paste a built /search/results/content/ URL and get the posts on it (the node parses the URL into the same filter object as search-posts). Cursor-paginated; page on with paging.next_cursor. Cost 2 credits.
Contract:
- MCP tool
scrape_linkedin_search_posts_by_url, 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_search_posts_by_url.
MUST start with https://www.linkedin.com/search/results/content/ (422 invalid_search_url otherwise).
2048Preferred 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.
128Rows per page (1..100); default 10.
1 <= x <= 100Opaque resume token from paging.next_cursor; null/omitted = first page.
2048