Read LinkedIn Profile Posts · Ploid

Provide one person's LinkedIn profile URL, vanity slug or @handle. The request reads available posts from that personal profile. Company-page posts and comments the person left elsewhere are separate tasks, so do not substitute those identifiers.

No. limit is a maximum between 1 and 20, not a minimum or guaranteed count. A shorter result does not identify why fewer posts were supplied, and increasing the maximum does not establish complete history.

When actual figures are supplied, the Agent can compare matching metrics across the returned posts. Preserve the source labels and keep missing values distinct from zero. Counts alone do not establish a unique audience, an engagement rate, content quality or people's intentions.

This request accepts a profile identifier and an optional maximum. It has no date-range or continuation input. Do not turn a supplied post date into a retrieval filter or treat the returned set as all posts from a period.

Use it as post-reading material. It does not establish a complete discussion thread, the person's full profile or all their activity. If the brief needs background details or thread context, gather those through a separate supported task and distinguish them from the returned posts.

An empty or unavailable result does not explain its cause or prove inactivity. Do not infer deletion, privacy settings or a permanent access problem from the gap. Record that the reading material was missing rather than inventing posts or activity conclusions.