Fresh Linkedin Profile Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_company_by_urlD | 1 credit per call. |
| enrich_leadD | 1 credit per call. Using each extra option will cost another 0.5 credits. Maximum: 3 credits. |
| get_company_by_idD | 1 credit per call. |
| find_custom_headcountB | Discover the count of employees within a specific company who meet designated criteria. 1 credit per call. |
| countB | Get the number of job openings a company has posted on LinkedIn. 1 credit per call. |
| google_profilesD | 2 credits per call. |
| get_profile_pdf_cvD | 1 credit per call. |
| get_open_to_work_statusD | 1 credit per call. |
| search_companiesC | Step 1: Use this endpoint to make a search using your criteria. This endpoint will return a \ |
| get_search_resultsC | Get search results. Please make sure the search is \ |
| search_leadsC | Find and scrape lead details with advanced filters. |
| search_postsD | 2 credits per call. |
| get_posts_reactionsD | 1 credit per call. |
| get_posts_commentsD | 1 credit per call. |
| get_profile_latest_post_dateC | Find out when he/she posted recently. |
| detect_activity_timeB | Get the time of the latest profile activity. 2 credits per call. |
| search_decision_makersB | Search for decision makers of any company. |
| lead_search_at_scaleB | Find and scrape leads at scale |
| search_jobs_v2C | Using a simpler payload. 1 credit per call. |
| check_search_statusB | Get the status of your search using the request_id given in step 1. |
| get_post_detailsB | Scrape details of a single post based on its URN. |
| get_job_detailsA | Scrape the full job details, including the company basic information. 1 credit per call. |
| get_companys_postsD | 2 credits per call. |
| get_companiesD | Get search results. Please make sure the search is \ |
| check_company_search_statusC | Get the status of your search using the request_id given in step 1. |
| search_companies_by_sn_urlC | Provide URL instead of filters. |
| search_jobsD | To scrape all results from each search, change the parameter \ |
| get_company_insightsD | 5 credits per call. |
| get_profiles_postsC | 2 credits per call |
| get_company_by_domainD | 1 credit per call. |
| search_linkedin_school_pages_via_googleB | Find up to 100 schools that match your criteria via Google. 2 credits per call. |
| search_linkedin_company_pages_via_googleC | Find up to 100 companies that match your criteria via Google. 2 credits per call. |
| get_years_of_experienceB | Get the total number of years of experience of a profile. |
| get_recommendation_receivedA | Get profile’s recommendations (received). 1 credit per call. |
| search_companies_instantlyA | Search companies in our cached database of 64 million records (updated annually). Instant results. Cost: 1 credit for 10 companies (searches returning fewer than 10 results still consume 1 credit). |
| get_recommendation_givenC | Get profile’s recommendations (given). 1 credit per call. |
| search_leads_v2D | Provide search url instead of filters |
| get_open_profile_statusD | 1 credit per call. |
| get_extra_profile_dataB | Get more profile’s data fields like languages, top skills, certifications, publications, patents, awards |
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 39 tools
There are multiple overlapping company and lead search tools (search_companies, get_companies, search_companies_instantly, search_companies_by_sn_url, search_leads, search_leads_v2, lead_search_at_scale), some with identical 'Get search results' descriptions. While many retrieval tools are distinct, the boundary between async search, status, and result-fetching endpoints is easy for an agent to confuse.
The set mixes get_* and search_* patterns with exceptions like count, enrich_lead, find_custom_headcount, google_profiles, and lead_search_at_scale. It also contains inconsistent v2 suffixes, generic names, and the typo get_companys_posts, making the naming pattern unreliable.
39 tools is far beyond the typical well-scoped MCP surface, even for a broad LinkedIn data product. The count feels bloated largely because search functionality is split across many overlapping variants rather than consolidated.
For a read-only LinkedIn data enrichment server, the surface covers companies, profiles, posts, jobs, leads, decision makers, and school/company searches quite thoroughly. Minor gaps exist, such as no explicit employee-list or full profile-experience endpoint, but most lead-generation workflows have no dead ends.