linkedin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_CLIENT_ID | Yes | LinkedIn app Client ID | |
| LINKEDIN_CLIENT_SECRET | Yes | LinkedIn app Client Secret |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check whether the tool is authorized to post, and as which member. |
| publish_nowA | Publish a text post to your LinkedIn profile immediately. text: the full post body. visibility: PUBLIC (default) or CONNECTIONS. |
| schedule_postA | Queue a post for later. It is published by the scheduler process. when: ISO time ('2026-08-20T09:00') or relative ('+2h', '+1d').
Run the scheduler (cron or |
| list_postsB | List posts. kind: 'scheduled', 'published', or 'all'. |
| cancel_scheduledA | Remove a queued post by its id. |
| post_briefA | Get a structured brief + rules to write a strong post on a topic. archetype: build_in_public | lesson | teardown | opinion | result. Use the returned structure and rules to write the actual post, then publish_now or schedule_post it. |
| content_calendarC | A safe weekly posting cadence and best-practice rules for steady growth. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: auth_status checks authorization, publish_now posts immediately, schedule_post queues for later, list_posts retrieves posts, cancel_scheduled removes queued posts, post_brief gives content guidance, and content_calendar provides a posting cadence. No two tools overlap in function.
Naming mixes verb-first patterns (publish_now, schedule_post, list_posts, cancel_scheduled) with noun-first patterns (auth_status, post_brief, content_calendar). All are snake_case and readable, but the verb/noun order is inconsistent.
With 7 tools, the set is well-scoped for a LinkedIn posting server. Each tool earns its place without unnecessary bloat, covering authentication, publishing, scheduling, listing, canceling, and content guidance.
The core lifecycle is covered: create (publish/schedule), read (list), and delete (cancel scheduled). Missing operations like deleting published posts or editing scheduled posts are minor and can be worked around via cancel-and-recreate.