Skip to main content
Glama
abhineet34

linkedin-mcp-server

List LinkedIn Posts

linkedin_list_posts
Read-onlyIdempotent

List posts from a LinkedIn member or company page using their unique URN. Paginate through results and choose markdown or JSON output.

Instructions

List posts by a LinkedIn member or organization.

NOTE: Listing posts requires the r_member_social scope (member) or r_organization_social scope (org). These are approval-gated scopes. For org posts, you also need to be an admin of the organization.

Requires scope: r_member_social or r_organization_social

Args:

  • author_urn (string): Author URN — 'urn:li:person:{id}' or 'urn:li:organization:{id}'

  • limit (number): Max posts to return, 1–50 (default: 20)

  • offset (number): Posts to skip for pagination (default: 0)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: { "total": number, "count": number, "offset": number, "items": [Post], "has_more": boolean, "next_offset": number }

Error Handling:

  • 403 if r_member_social / r_organization_social scope is missing or not approved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
author_urnYesURN of the author whose posts to list. Use 'urn:li:person:{id}' for members or 'urn:li:organization:{id}' for companies.
limitNoMaximum number of posts to return (1–50, default: 20)
offsetNoNumber of posts to skip for pagination (default: 0)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior5/5

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

Annotations already indicate read-only, idempotent, not destructive. The description adds substantial value: scope requirements, error handling (403), return structure with pagination fields (total, count, offset, has_more, next_offset), and output format options.

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?

The description is well-organized into sections (NOTE, Requires scope, Args, Returns, Error Handling). Each section is concise and informative without being bloated. A bit longer than ideal but well-structured.

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 tool with 4 parameters, no output schema, and no nested objects, the description covers all necessary aspects: prerequisites, parameter details, return format with pagination, and error handling. It is complete and self-contained.

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?

Schema description coverage is 100%, so baseline is 3. The description adds contextual meaning beyond schema: it clarifies scope dependency for author_urn, documents default values and constraints for limit/offset, and explains response_format purpose.

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?

The description clearly states 'List posts by a LinkedIn member or organization' — a specific verb and resource. It distinguishes from sibling tools like create, delete, get, and update posts by its listing function.

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?

The description explicitly mentions required scopes (r_member_social, r_organization_social) and admin status for org posts. It does not discuss when not to use, but the prerequisites are clear and helpful.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/abhineet34/linkedin-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server