Skip to main content
Glama

LinkedIn People Search

run_linkedin_people_search
Read-onlyIdempotent

Searches LinkedIn people using an optional free-text query and a rich set of advanced filters (company, title, seniority, location, experience, industry).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_linkedin_people_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
lastNamesNo
locationsNo
startPageNoPage offset to start from.
firstNamesNo
maxResultsNoMaximum number of results to return.
industryIdsNo
pastCompanyNo
scraperModeNoScraper depth mode, e.g. 'short' or 'full'.
searchQueryNoFree-text people search query.
pastJobTitleNo
currentCompanyNo
functionFilterNo
seniorityLevelFilterNo
currentJobTitleFilterNo
companyHeadcountFilterNo
yearsOfExperienceFilterNo
yearsAtCurrentCompanyFilterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds essentially nothing behavioral beyond that: no rate limits, no pagination behavior, no explanation of scraperMode depth, and no note on what 'optional' query means for result breadth.

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?

A single, front-loaded sentence with no filler; the parenthetical filter list is dense but earns its place by enumerating capabilities. Nothing is wasted, though it could be slightly more scannable.

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 17-parameter tool with 0 required params, 24% schema coverage, no enums, and no output schema, the one-sentence description is far too thin. An agent cannot infer accepted value formats, pagination via startPage/maxResults, or how the free-text query interacts with the structured 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?

Schema description coverage is only 24%, so the description must carry weight, and it partially does by naming filter categories (company, title, seniority, location, experience, industry) that map onto params like currentCompany, seniorityLevelFilter, and locations. It still leaves half the parameters (lastNames, firstNames, pastCompany, functionFilter, companyHeadcountFilter, scraperMode, startPage, maxResults) without meaning, and adds no value-format or syntax detail.

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?

States a specific verb (searches) and resource (LinkedIn people) and enumerates the filter categories, so an agent can immediately tell what the tool returns. It does not, however, distinguish itself from adjacent siblings like run_linkedin_company_employee or run_linkedin_email, which also surface people-related data.

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 offers no when-to-use guidance, no prerequisites, and no mention of alternatives within the large LinkedIn sibling family. It simply asserts what the tool does without helping the agent decide whether to pick it over run_linkedin_company_search or the enrichment tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources