REST API
Collect a post's engagers
Shorthand for create_monitor: collect the commenters of ONE LinkedIn post now.
POST
/v1/monitors/collectParameters
urlstringrequiredthe LinkedIn post URL
namestringoptionalclientstringoptionalAGENCIES: the client this monitor belongs to (defaults to the key’s binding). A subscription can only scope a monitor of its own client or an organization-wide one.
sources"comments" | "reactions"[]optionaldefault [‘comments’]; add ‘reactions’ for the likers (80 records each when delivered or listed, a commenter 40) (up to 2 items)
resolve"all" | "index_only" | "none"optionalmax_engagersintegeroptional(min 10, max 20000)
prefilterobjectoptionalexcludeobjectoptionalalias of prefilter (preferred): drop people by name / headline before anything is read, e.g. {headline:{contains:[‘recruiter’,‘student’]}}
What your agent reads
The tool description exactly as an MCP client receives it in tools/list — it doubles as the full behaviour of the endpoint.
Shorthand for create_monitor({kind:'post', collect:{after:'0s'}}): collect the commenters (and, with sources ['comments','reactions'], the likers) of ONE LinkedIn post now. Returns the monitor; the people appear in list_monitor_people within minutes and in any subscription scoped to the monitor. PRICE: collecting and resolving are our cost; you pay per person DELIVERED or LISTED — a commenter 40 records, a reactor (liker) 80, once per person per monitor however you take them; a watched profile's daily look 40 records whether or not a subscription exists (a profile monitor with no subscription for 7 days is paused); an e-mail found +2 (find_email).
Errors follow one format.