Skip to main content
Glama
felipfr

LinkedIn MCP Server

by felipfr

search_people

Find LinkedIn professionals using advanced filters such as keywords, name, company, job title, location, industry, and education. Ideal for targeted networking and research.

Instructions

Search LinkedIn professionals with advanced filters and criteria

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNameNoCurrent company name
firstNameNoFirst name
industryNoIndustry
keywordsNoSearch keywords
lastNameNoLast name
locationNoLocation
schoolNoSchool/university
titleNoJob title

Implementation Reference

  • src/server.ts:68-82 (registration)
    Registers the MCP tool 'search-people' with description, input schema, and an async handler that delegates to clientService.searchPeople and formats the response.
    this.server.tool(
      'search-people',
      'Search for LinkedIn profiles based on various criteria',
      linkedinApiSchemas.searchPeople,
      async (params) => {
        this.logger.info('Executing LinkedIn People Search', { keywords: params.keywords })
        try {
          const results = await this.clientService.searchPeople(params)
          return this.createResourceResponse(results)
        } catch (error) {
          this.logger.error('LinkedIn People Search Failed', error)
          throw error
        }
      }
    )
  • Core implementation of the people search logic: builds query parameters from input and makes authenticated GET request to LinkedIn /search/people endpoint.
    public async searchPeople(params: SearchPeopleParams): Promise<SearchPeopleResult> {
      const queryParams = new URLSearchParams()
    
      const paramMapping: Record<string, string | undefined> = {
        keywords: params.keywords,
        location: params.location
      }
    
      Object.entries(paramMapping)
        .filter(([_, value]) => value !== undefined)
        .forEach(([key, value]) => queryParams.append(key, value as string))
    
      this.appendArrayParams(queryParams, {
        'current-company': params.currentCompany,
        'facet-industry': params.industries
      })
    
      return this.makeRequest<SearchPeopleResult>('get', `/search/people?${queryParams.toString()}`)
  • Zod schema defining the input parameters for the search_people tool, used for validation in MCP.
    searchPeople: {
      currentCompany: z.array(z.string()).optional().describe('Filter by current company'),
      industries: z.array(z.string()).optional().describe('Filter by industries'),
      keywords: z.string().optional().describe('Keywords to search for LinkedIn Profiles'),
      location: z.string().optional().describe('Filter by location')
    },
  • TypeScript interface defining the SearchPeopleParams used in the service method signature.
    export interface SearchPeopleParams {
      keywords?: string
      location?: string
      currentCompany?: string[]
      industries?: string[]
    }
  • TypeScript interface defining the expected SearchPeopleResult from LinkedIn API.
    export interface SearchPeopleResult {
      people: LinkedInProfile[]
      paging: {
        count: number
        start: number
        total: number
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'search' implies a read-only operation, the description doesn't address critical aspects like authentication requirements, rate limits, result format, pagination, or LinkedIn API constraints. The mention of 'advanced filters' is vague without explaining what makes them advanced.

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

Conciseness4/5

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

The description is a single, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for a search tool, though it could be slightly more informative given the lack of annotations and output schema.

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

Completeness2/5

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

For a search tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what results look like, how many results are returned, whether authentication is required, or how the search actually works on LinkedIn. The mention of 'advanced filters' is too vague to be helpful.

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 8 parameters are documented in the schema. The description adds minimal value beyond the schema by mentioning 'advanced filters and criteria' but doesn't provide additional context about parameter interactions, search logic, or which filters are most effective. Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose4/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 target resource ('LinkedIn professionals'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling search tools like 'search_jobs' beyond the resource type, missing explicit distinction.

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?

The description mentions 'advanced filters and criteria' but provides no guidance on when to use this tool versus alternatives like 'get_connections' or 'search_jobs'. There's no indication of prerequisites, limitations, or typical use cases for this specific search functionality.

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

Related 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/felipfr/linkedin-mcpserver'

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