REST API
Read a people list
The people on one of your people lists, newest first, with the fields you ask for.
GET
/v1/people-lists/:list_id/itemsParameters
list_idstringrequiredfields"linkedin" | "member_id" | "person_id" | "name" | "headline" | "title" | "title_source" | "seniority" | "function" | "company_domain" | "company_name" | "company_linkedin" | "country" | "email" | "email_status" | "source" | "source_ref" | "added_at" | "updated_at" | "last_checked_at" | "check_snapshot" | "snapshot"[]optionalany of linkedin, member_id, person_id, name, headline, title, title_source, seniority, function, company_domain, company_name, company_linkedin, country, email, email_status, source, source_ref, added_at, updated_at, last_checked_at, check_snapshot, snapshot (up to 22 items)
source"monitor" | "import" | "api"optionalsincestringoptionalISO date-time: people added after it
cursorstringoptionallimitintegeroptionaldefault 50 (min 1, max 500)
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.
The people on one of your people lists, newest first, with the fields you ask for (default: profile URL, name, headline, title, seniority, function, company, country, e-mail + status, source, added_at). RECORD COST: 1 person_row per person returned when e-mail fields are among `fields` (the default); ask for fields without email / email_status to read the list for free. Page with cursor (≤ 500 per page).
Over REST, parameters go in the query string.
Errors follow one format.