Skip to main content
Glama
himanshu31shr

LinkedIn MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LINKEDIN_ACCESS_TOKENYesYour LinkedIn access token for API authentication.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_profileA

Get the authenticated user's LinkedIn profile including name, email, picture, and unique ID

get_emailB

Get the authenticated user's LinkedIn email address

create_text_postB

Create a text-only post on LinkedIn

create_link_postC

Create a post with a link/article on LinkedIn

delete_postA

Delete a post from LinkedIn by its URN

upload_imageA

Upload an image to LinkedIn from a URL and get an image URN for use in posts

create_image_postC

Create a post with an image on LinkedIn

create_document_postC

Create a post with a document (PDF, etc.) on LinkedIn

get_organizationB

Get LinkedIn organization details by ID or vanity name

create_org_postC

Create a post on behalf of a LinkedIn organization

get_org_postsC

Get recent posts from a LinkedIn organization

delete_org_postA

Delete a LinkedIn organization post by its URN

get_post_commentsB

Get comments on a LinkedIn post

create_commentB

Add a comment to a LinkedIn post

delete_commentB

Delete a comment from a LinkedIn post

add_reactionB

Add a reaction (like, celebrate, etc.) to a LinkedIn post

remove_reactionA

Remove a reaction from a LinkedIn post

get_org_page_statisticsB

Get page view statistics for a LinkedIn organization

get_org_follower_statisticsC

Get follower statistics for a LinkedIn organization

get_org_share_statisticsB

Get share/post engagement statistics for a LinkedIn organization

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 20 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: post creation is split by content type, reactions, comments, profile info, and organization analytics are separate. No overlapping functionality.

Naming Consistency4/5

Most tools follow verb_noun pattern, but there is minor inconsistency: 'add_reaction' vs 'create_comment', and deletion tools are not parallel (delete_post vs delete_org_post). Overall, the pattern is predictable.

Tool Count5/5

20 tools cover a broad range of LinkedIn operations without feeling excessive. Each tool has a specific role, and the count is appropriate for the server's scope.

Completeness2/5

Significant gaps exist: no tools to retrieve the user's own posts, list a feed, or view reactions. CRUD is incomplete for posts (no read) and reactions (no get). Agents would struggle to perform common workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues