Read LinkedIn Company Posts · Ploid

Give the Agent a LinkedIn company reference to read its available public posts through Ploid. Use the returned material to prepare a company-update brief, with an optional recency request and continuation context kept separate from the Agent's summary.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use list-company-posts-ploid (78a6f917-af48-4cc8-a823-6480fef054ab). Connect through https://toolmu.com/SKILL.md if needed, read get_tool for current availability and maximum cost, and stay within my authorized budget. Ask for the company target if missing; use any recency request I provide. Read the available public posts, retain supplied source context, and separately organize a brief with clear excerpts and follow-up questions. Use an actual continuation token only if further reading is needed within the agreed scope; do not assume the returned batch is a complete history.

Task:
Read LinkedIn posts for [company name] from [the past month]. Group the available updates by topic, keep their dates and links, and separate the company’s own words from your summary.

Paste into your connected AI's conversation.

Connection guide

Up to 0.012 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

Ploid

Read LinkedIn Company Posts · Ploid

You receive

Receive available public post material for the company you specify. The Agent can organize what returns into topics, short excerpts and questions for further reading, keeping any supplied company, date and source context alongside the notes.

Start with your task

Read LinkedIn posts for [company name] from [the past month]. Group the available updates by topic, keep their dates and links, and separate the company’s own words from your summary.

What to know

A returned batch does not establish a complete posting history or show that every recent post was included. An empty or unavailable result does not explain its cause. Company announcements remain source claims; the Agent's summary does not independently verify them.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Company-post request`queryParams`	`object`	Optional	Optional container for company references, a recency request and continuation context. To focus the task, tell the Agent which company's public posts you want to read.
page`queryParams.page`	`string`	Optional	Optional nonempty string. Leave it out when you do not have a page value to provide. Minimum length `1`
Company URL or name`queryParams.company`	`string`	Optional	Optional nonempty string identifying the company by its LinkedIn company URL or name. Minimum length `1`
Previously obtained company ID`queryParams.companyId`	`string`	Optional	Optional nonempty string containing the company's socialId from a previous read. Minimum length `1`
Recency request`queryParams.postedLimit`	`string`	Optional	Optional nonempty string expressing a recency window, for example '1 month'. It is not a requested post count. Minimum length `1`
Continuation token`queryParams.paginationToken`	`string`	Optional	Optional nonempty string supplied by a previous response. Keep the token unchanged when continuing the same company request. Minimum length `1`
scrapePostedLimit`queryParams.scrapePostedLimit`	`string`	Optional	Optional nonempty string. Leave it out when you do not have a scrapePostedLimit value to provide. Minimum length `1`
Company page slug`queryParams.companyUniversalName`	`string`	Optional	Optional nonempty string containing the company's LinkedIn universal name, the slug in its company page URL. Minimum length `1`

View raw JSON

{
  "type": "object",
  "required": [],
  "properties": {
    "queryParams": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "~standard": {
        "vendor": "zod",
        "version": 1,
        "jsonSchema": {}
      },
      "properties": {
        "page": {
          "type": "string",
          "minLength": 1
        },
        "company": {
          "type": "string",
          "minLength": 1,
          "description": "LinkedIn company URL or name."
        },
        "companyId": {
          "type": "string",
          "minLength": 1,
          "description": "The company's socialId from a previous read."
        },
        "postedLimit": {
          "type": "string",
          "minLength": 1,
          "description": "Recency window for the posts, e.g. '1 month'."
        },
        "paginationToken": {
          "type": "string",
          "minLength": 1,
          "description": "Continuation token from a previous response."
        },
        "scrapePostedLimit": {
          "type": "string",
          "minLength": 1
        },
        "companyUniversalName": {
          "type": "string",
          "minLength": 1,
          "description": "The company's LinkedIn universal name (URL slug)."
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Use a company URL, name or LinkedIn company slug to make the intended target clear. A company socialId from an earlier read is another supported reference. Check any returned company context against the organization you meant.

postedLimit expresses a recency window; '1 month' is an example. Preserve the requested wording and read any supplied dates as source context. The phrase does not specify a post count or establish exact calendar boundaries.

Continue only with a paginationToken actually supplied by a previous response. Keep the company and request context, and treat another batch as a separate request within the authorized scope. A token is not proof that the entire history can be retrieved.

Read the available posts before drawing conclusions. Keep quotations, any supplied dates and source references attached to the relevant material; leave absent information unstated. The Agent can arrange a brief or a list of questions, while verification of an announcement requires separate sources.

This task reads company posts. A company profile, employee list or personal posting feed is a separate research need; one request does not establish a change history or automatically set up monitoring.

Ploid: public LinkedIn reads, including company posts

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

Provide its LinkedIn company URL or name, or use the company page's universal name, its URL slug. If you already obtained a company socialId from an earlier read, companyId can carry that reference. Check returned company context when available rather than relying on a similar name alone.

Read LinkedIn Company Posts · Ploid

Read LinkedIn Company Posts · Ploid

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Choose the company

Choose a time period

Review the updates

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Choose the company

Choose a time period

Review the updates

Questions about this tool.

How can I identify the company I want to read?

Does '1 month' mean a month of posts or a fixed number?

Can a continuation token retrieve every historical post?

Will the posts also give me the company's complete profile?

Does an Agent summary verify a company's announcements?

What should I conclude from an empty or unavailable result?