read-linkedin-network) is available in AI Chat and through authorized MCP and ChatGPT access. It requires workspace membership, permission to use the selected account and a working LinkedIn Classic connection. An MCP account selection stays pinned to that account. Sales Navigator or Recruiter alone does not establish eligibility.
Each call reads one current page: 20 entries by default, at most 100. Keep the same selected account, list and name filter when continuing. A short page does not prove that Connie retrieved the full network. Missing totals or continuation data leave completeness unknown. An empty page means only that this page returned no entries; it is separate from unavailable data or a failed provider request. When an incomplete page cannot advance, retry the same page later instead of skipping entries. Lists can change while you page through them.
Results include readable names, stable LinkedIn
providerId values and available public profile identifiers or links. These can identify someone in a subsequent authorized tool call; they do not authorize sending messages or changing relationships.
Existing tool permissions, per-call credit pricing and rate limits apply to each page. Wait and retry after a rate limit; reconnect the selected Classic account if its connection is unavailable. A failed request is reported as a failure rather than an empty network.
The new reader is excluded from Workflow Actions, Workflow Agents, Records columns and programs. Existing List LinkedIn connections configurations retain their existing behavior. Public people discovery continues to use the existing people-search tools. This reader does not follow, unfollow, remove connections or send invitations.
For MCP, use connector-list-accounts to select the account, then discover read-linkedin-network with search-tools or inspect its full schema with get-tool. Use relationship: "connections" with optional search and cursor, or relationship: "followers" / "following" with optional offset. No target-user argument is accepted. It remains callable through authorized direct or wrapped invocation even when absent from the connector’s compact initial tool list.
Read comments written by one person
Ask Connie to show the comments this person wrote on LinkedIn. Connie first resolves the exact person with the existing people-search/profile tools and asks you to clarify namesakes. Choose the acting connected LinkedIn account when several are available. This separate reader,read-linkedin-user-comments, requires a working Classic connection and permission to use that account; MCP account pins remain enforced.
The reader accepts person as the selected get-profile.data.profile_link, extract-linkedin-profile.data.public_profile_url, or a verified Classic ACo… member ID such as read-linkedin-network.items[].providerId. Numeric linkedin_id values and Sales Navigator/Recruiter IDs are not assumed compatible: use the selected person’s public profile link. Use person: "me" for the freshly verified connected owner. No similar-name substitution is allowed.
Results describe comments authored by that person across posts, including supplied reply context. Each comment includes its ID, text, provider timestamp and author, plus parent-post ID/link when available. Missing or restricted parent data, timestamps and thread information stay unavailable; Connie does not construct links or dates. An absent thread ID does not establish that a comment is top-level. These reads do not return comments received on someone’s posts or the posts they reacted to.
Each call reads one page, default 20 comments and maximum 100. Start at offset 0. Copy pagination.nextCursor unchanged when present, otherwise nextOffset, keeping person, account and limit unchanged. Never send offset and cursor together. Offset advances by rows actually returned. Short pages remain partial. Explicit provider end/total evidence can mark complete for the provider-visible traversal only; no full historical coverage is promised. Empty without end evidence is no_visible_comments or incomplete; confirmed empty is no_comments, and a confirmed later end is end_of_visible_results. Restrictions and provider failures are errors, not empty results. Date, keyword, post and sorting filters are unsupported and rejected.
Use search-tools to discover the reader and get-tool to inspect its exact schema. Authorized direct and supported wrapped MCP/ChatGPT calls use the same account/access/billing gates even when the reader is absent from the compact initial list. AI Chat and authorized MCP/ChatGPT are the only supported surfaces. Workflow Actions/Agents, Records columns and programs cannot discover or execute it. It does not save Records, mutate comments, react, send outreach, schedule monitoring or add media.
Configured tool pricing applies per call independently of any profile lookup. Read-only does not mean free. Release status: implemented locally; initial catalog enablement is held until a per-call price is reviewed. Production catalog/embeddings, deployment, real-client verification and settled live billing have not been published or verified.