Skip to main content
Glama
Sign In

Publora

by com.publora
OverviewDiscussionsAdmin

company list linkedin page posts

company_list_linkedin_page_posts
Read-onlyIdempotent

List published posts authored by a connected LinkedIn Company Page in ONE Workspace. Use its connection id from company_list_channels. Items contain canonical postedId (share/ugcPost URN), original permalink, text, sourceSnapshot and reshare flags; use postedId verbatim for draft.platformSettings.linkedin.repostParentUrn and copy sourceSnapshot to draft.repostSourceSnapshot for the client approval preview. Follow paging.nextStart with the same connection, count and sortBy until null; an empty/short page can still have a next page. Does not list personal-profile posts or resolve arbitrary LinkedIn URLs. Read-only: creates no draft, review or publication.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>",
      "connectionId": "<connectionId>"
    },
    "name": "company_list_linkedin_page_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
startNo
sortByNo
workspaceIdYesExact ID returned by a Company tool; never a personal platformId
connectionIdYesExact ID returned by a Company tool; never a personal platformId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), the description adds a non-obvious paging quirk ('an empty/short page can still have a next page') and reasserts that no draft, review, or publication is created. It also tells the agent what the returned items contain, which the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and each sentence carries operational value (dependency, return fields, pagination, exclusions, read-only guarantee). It is dense in a single paragraph and could be split for scanability, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no output schema and only 40% parameter coverage, the description supplies everything an agent needs: prerequisite source for the connection id, item shape, exact downstream usage of postedId and sourceSnapshot, and the termination rule for pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 40%, the description compensates by explaining that connectionId must come from company_list_channels, that paging must reuse the same connection, count, and sortBy via nextStart, and how postedId maps into draft.platformSettings.linkedin.repostParentUrn. Minor format details for count/start/sortBy bounds remain only in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope: 'List published posts authored by a connected LinkedIn Company Page in ONE Workspace.' It also explicitly excludes personal-profile posts and arbitrary URL resolution, which separates it from the many other post-listing siblings (company_list_posts, list_posts, get_post).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete prerequisite (use the connection id from company_list_channels) and explicit exclusions, plus paging instructions on when to keep going. It stops short of naming the alternative tool for personal-profile posts, so the routing is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Publora toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources