Li Data Scraper 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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_public_profile_data_by_urlC | Enrich public profile data |
| get_company_detailsC | The endpoint returns enrich company details |
| get_company_by_domainB | Enrich company data by domain. 1 credit per successful request. |
| search_peopleC | You may see less than 10 results per page. This is because not all profiles as public, sometimes hiding profiles. The endpoint automatically filters these profiles from the result |
| about_the_profileB | Get profile verification details, profile’s joined, contact information updated, and profile photo updated date |
| get_profile_data_and_connection_u0026_follower_countC | Get Profile Data and Connection \u0026 Follower Count |
| get_post_comment_reactionC | Get post comment Reaction |
| search_post_by_keywordC | Search Post by Keyword |
| get_post_reactionsB | Get profiles that reacted to the post |
| get_profile_post_and_commentsC | Get profile post and comments of the post |
| get_profiles_commentsB | Get last 50 comments of a profile. 1 credit per call |
| get_company_jobsC | Get company jobs |
| pingD | Ping |
| get_profile_recent_activity_timeB | Get the time of the profile's last activity |
| get_profile_reactionsB | Find out what posts a profile reacted to |
| get_profile_post_commentB | Get 50 comments of a profile post (activity) |
| get_profiles_postsB | Get last 50 posts of a profile. 1 credit per call |
| search_post_by_hashtagD | Search Post by Hashtag |
| get_company_post_commentsB | Get comments of a company post |
| get_companys_postB | Get last 50 posts of a company. 1 credit per call |
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 20 tools
There is significant overlap between tools targeting similar resources, such as get_profile_post_and_comments, get_profile_post_comment, and get_profiles_comments, which could confuse an agent about which to use for profile comments. However, descriptions help differentiate some tools, like distinguishing company vs. profile operations, preventing complete ambiguity.
Naming is inconsistent with mixed patterns: most tools use get_* or search_* prefixes, but about_the_profile deviates, and some names are overly verbose or include escaped characters (e.g., get_profile_data_and_connection_u0026_follower_count). This lack of a uniform convention reduces predictability and readability.
With 20 tools, the count is borderline high for a data scraper server, feeling slightly heavy but not extreme. It covers multiple domains (profiles, companies, posts, searches), which justifies some volume, but could benefit from consolidation to avoid overlap and improve coherence.
The tool set provides broad coverage for LinkedIn data scraping, including profile, company, post, comment, reaction, and search operations, with minor gaps such as missing update or delete tools (expected for read-only scraping) and no direct tool for managing credits or errors. Overall, it supports core workflows without major dead ends.