Skip to main content
Glama
EgiStr

linkedin-mcp

by EgiStr

List LinkedIn Posts

linkedin_list_posts
Read-onlyIdempotent

Fetch a member's LinkedIn posts, newest-first, with pagination. Use to retrieve posts for the authenticated user or a specific member ID, choosing markdown or JSON format.

Instructions

List LinkedIn posts for a member.

Returns posts published by the specified member (or the authenticated user by default). Posts are returned newest-first with pagination support.

Args:

  • member_id (string, optional): LinkedIn member ID (sub) to fetch posts for

  • start (number): Start index for pagination (default: 0)

  • count (number): Number of posts to return, max 50 (default: 10)

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

Returns (JSON format): { "total": number, // Total posts available "count": number, // Posts in this response "start": number, // Current offset "has_more": boolean, // Whether more pages exist "next_offset": number, // Offset for next page "posts": [{ "id": string, // Post ID "text": string, // Post commentary/text "author": string, // Author URN "created": string, // Human-readable date "created_timestamp": number, // Unix timestamp ms "visibility": string,// Visibility setting "url": string // Direct link }] }

Requires scope: r_member_social or r_organization_social

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of posts to return (max 50)
startNoStart index for pagination
member_idNoLinkedIn member ID (sub) to fetch posts for. Defaults to authenticated user
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already mark the tool as read-only and idempotent. The description goes well beyond that by disclosing pagination semantics, ordering (newest-first), scopes required (r_member_social/r_organization_social), and the exact JSON response structure including fields like total, has_more, and next_offset. There is no contradiction with annotations.

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

Conciseness5/5

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

The description is front-loaded with the core purpose, then provides structured Args and Returns sections that are dense but not verbose. Every section earns its place, especially the response JSON sample, which is essential because there is no output schema.

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?

The description is self-sufficient for an agent: it explains default behavior, member targeting, pagination, maximum count, output format options, required scopes, and the full response shape. Since no output schema exists, the detailed JSON return specification fills exactly that gap.

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

Parameters3/5

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

Schema description coverage is 100%, so each parameter is already documented in the schema. The description's Args section largely repeats defaults and meanings already present in the schema (count max 50, start defalt 0, response_format enum), adding little semantic value beyond what the input schema provides.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('LinkedIn posts for a member'), and specifies that it returns posts published by the specified member or the authenticated user by default. It does not explicitly contrast itself with sibling tools like linkedin_get_feed, so it stops short of full explicit sibling differentiation.

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 gives clear invocation context: it lists posts for a specified member, defaults to the authenticated user, and explains pagination behavior with start/count/next_offset. It does not explicitly state when to prefer this over linkedin_get_feed or linkedin_create_post, but the 'posts published by a member' framing makes the intended use obvious.

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

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/EgiStr/linkedin-mcp'

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