linkedin-discovery-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_linkedin_profilesA | Discover public LinkedIn profiles matching the given criteria, via DuckDuckGo's public search (site:linkedin.com/in). Does NOT log into or scrape LinkedIn directly, so it carries no LinkedIn account risk. Returns ranked candidates with name/headline/company/location best-effort parsed from search snippets, plus a match_score and matched_signals showing why each candidate ranked where it did. Data is shallow (no full work history, no contact info) — treat results as a shortlist to verify manually, not verified enriched profiles. DuckDuckGo's LinkedIn index is smaller than Google's, so narrow criteria can come back with few or zero results — broaden them if that happens. Paced by a self-imposed daily request budget to stay polite to DuckDuckGo. |
| get_search_quota_statusA | Reports how much of today's self-imposed DuckDuckGo request budget has been used and how much remains. Check this before large search batches so you don't burn budget you need later in the day. |
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 2 tools
The two tools have clearly distinct purposes: one performs profile searches, the other reports quota status. There is no overlap or ambiguity between them.
Both tools follow the verb_noun snake_case pattern (search_linkedin_profiles, get_search_quota_status). The naming is consistent and predictable.
With only 2 tools, the server is on the thin side. The narrow scope (search + quota) makes it reasonable, but it feels minimal for a discovery-focused server.
The core search capability is present, but there are notable gaps: no way to fetch a specific profile's details, no explicit pagination, and no advanced filters beyond search criteria. The quota tool is a helpful addition but doesn't round out the surface.