Skip to main content
Glama
kaistenberg

MCP Server for LinkedIn

by kaistenberg

Search People

search_people
Read-only

Find LinkedIn profiles by keywords, location, company, and connection degree. Use filters to narrow results to specific networks or employers.

Instructions

Search for people on LinkedIn.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoOptional connection-degree filter. Each element is one of "F" (1st-degree), "S" (2nd-degree), "O" (3rd-degree and beyond). Example: ["F"] to only return 1st-degree connections.
keywordsYesSearch keywords (e.g., "software engineer", "recruiter at Google")
locationNoOptional location filter (e.g., "New York", "Remote")
current_companyNoOptional current-employer filter. LinkedIn's currentCompany facet only filters on the numeric company URN id (e.g. "1115" for SAP); plain company names are accepted by the URL but ignored by LinkedIn and return the unfiltered result set. Look up a company's URN via get_company_profile -- it is exposed under references["about"]. For company-wide employee demographics (location/education/function breakdown) plus a slug-based lookup, use get_company_employees instead.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description merely restates the purpose and adds no behavioral details beyond the annotations. Annotations declare readOnlyHint=true and openWorldHint=true, but the description does not mention result limits, pagination, or any search-specific caveats, so it fails to add informative value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-sentence description is immediate and free of extraneous words, effectively communicating the tool's core function in minimal space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema, an output schema, and annotations indicating read-only and open-world behavior, the terse description is adequate to convey the tool's basic purpose. However, it omits any mention of search-specific behavior like result ordering or how to scope searches, though the schema covers filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, all four parameters (keywords, network, location, current_company) are already explained in detail. The description adds no additional semantic context, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (search) and the resource (people on LinkedIn), distinguishing it from sibling search tools like search_jobs and search_companies by specifying 'people'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as get_person_profile for direct profile lookups or search_companies for organizations. The only hint is the name, which implies people search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kaistenberg/MCP-Linkedin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server