Unlinked
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_TOKEN | Yes | LinkedIn access token. Accepts 'Bearer <token>' or a bare token. | |
| LINKEDIN_API_VERSION | No | API version in YYYYMM format. Defaults to 202312. | 202312 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_get_profileA | Get the user's LinkedIn résumé: bio, work history, education, skills, certifications, projects, languages, awards, publications, and more. Use for questions about who they are professionally, their background, or qualifications. |
| linkedin_get_activityA | Get the user's LinkedIn social activity: connections, posts, articles, comments, likes, job applications, saved jobs, and job-search preferences. Use for questions about their network, content, or job search. Prefer specific sections — these can be large. |
| linkedin_get_sectionA | Get raw data for a single LinkedIn section by exact name. Use when you need one specific section or the raw API response. Section names are case-sensitive. |
| linkedin_get_recent_changesA | Get the user's LinkedIn data changes from the past 28 days (profile edits, new connections, etc.). Poll incrementally by passing the previous response's nextStartTime. If empty, run linkedin_check_access to verify consent. |
| linkedin_check_accessA | Check whether the user has granted LinkedIn data access to this app. Use to diagnose missing data or 403 errors before retrying other tools. |
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 serves a distinct purpose: profile retrieval, activity, raw section data, access check, and recent changes. No overlaps or ambiguity.
All tools follow the pattern 'linkedin_<verb>_<noun>', with verbs 'get' or 'check' and nouns indicating the resource. Consistent and clear.
Five tools is an appropriate size for a LinkedIn data server, covering core read operations without being excessive or too few.
The tool set covers profile, activity, specific sections, access verification, and change tracking. Missing write operations but the server is read-only, making the coverage comprehensive.