linkedin-mcp-custom
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check server health and version. |
| get_saved_jobsA | Get saved jobs from LinkedIn's /jobs-tracker/ page. Returns saved jobs raw text and a list of numeric job IDs. Pass any job_id to get_job_details for full posting text. |
| get_job_detailsA | Get full details for a specific LinkedIn job posting. |
| analyze_saved_jobsA | Full pipeline: scrape saved jobs -> EROI score -> KB write-back.
|
| close_session_toolB | Close the browser session and cleanup resources. |
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 5 tools
Each tool has a clearly distinct purpose: analyze_saved_jobs is a complex pipeline, get_saved_jobs lists jobs, get_job_details retrieves details, close_session_tool handles cleanup, and health_check is a utility. No overlap or ambiguity.
Naming is inconsistent: analyze_saved_jobs and close_session_tool use different conventions (the latter with a '_tool' suffix), while get_job_details and get_saved_jobs follow a standard verb_noun pattern, and health_check is a noun_noun. No consistent verb prefix or suffix style.
With 5 tools, the server is appropriately scoped for a LinkedIn jobs helper. It covers the main operations without overloading, though the health_check and close_session tools are minor utilities that add slight overhead.
The tool surface covers listing saved jobs, getting details, and an analysis pipeline, but lacks operations for removing or updating saved jobs, which are common in a jobs management context. The analysis tool is comprehensive but the rest is somewhat sparse.