LinkedIn Jobs MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_linkedin_jobsA | Search for jobs on LinkedIn with advanced filtering options. Returns job listings with position titles, company names, locations, salary information, and application links. |
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 1 tool
With only one tool, there is no possibility of ambiguity between tools. The tool's purpose is clearly described.
The single tool name 'search_linkedin_jobs' follows a clear verb_noun pattern, which is consistent and descriptive.
A single tool for a LinkedIn Jobs server is far too few. Expected tools for job details, applications, or filters are missing, making the server feel underdeveloped for its intended domain.
The tool set is severely incomplete, providing only search functionality. No tools for retrieving individual job details, applying, or managing job listings are present, leading to significant gaps.