Skip to main content
Glama
linkedin-scraper-mcp

linkedin-scraper-mcp

by Guaitolinii

Search People

search_people
Read-only

Search LinkedIn people by keywords and filter results by connection degree, location, current company, or a specific member's connections.

Instructions

Search for people on LinkedIn.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>"
    },
    "name": "search_people"
  }
}

Input 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. A single token ("F") or a comma-separated string ("F,S") is also accepted, for clients that cannot transmit an array.
keywordsYesSearch keywords (e.g., "software engineer", "recruiter at Google")
locationNoOptional location filter, as LinkedIn's numeric geo URN id (e.g., "103644278" for the United States). Plain-text place names are silently ignored by LinkedIn and return unfiltered results, so they are refused here. The id is the geoUrn value in the URL of a LinkedIn people search filtered to that place; without one, put the place in keywords instead.
connection_ofNoOptional profile id (e.g. "ACoAAB...") limiting results to that member's connections. Combine with network=["F"] to list the mutual connections you share with them; keywords may be "". Take the id from get_person_profile's "profile_urn"; a vanity name is refused, because LinkedIn ignores it and returns unfiltered results. LinkedIn also drops the filter, without saying so, when the member is 3rd-degree or beyond (you share no connections): the result is then your unfiltered network, not an empty list.
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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered, but the description adds no behavioral context such as result caps, pagination, or what an open-world search returns. The schema descriptions carry important caveats (e.g., silently ignored filters, dropped connection_of filter), but those live in the schema, not the description.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, but it is under-specified rather than efficient for a tool with five filters and open-world behavior. Conciseness here reflects minimalism that costs information rather than clarity gained.

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?

Although an output schema exists and the schema itself is richly annotated, the description provides no orientation for a moderately complex search tool with URN-based filters and filter-dropping edge cases. An agent reading only the description would not know how this relates to profile lookup or company-employee search.

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 100%, so the five parameters are fully documented in the schema, including URN requirements and silent-filter-drop behavior. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 names a specific verb and resource ("Search for people on LinkedIn"), which cleanly separates it from search_companies and search_jobs by resource type. It stops short of explicitly contrasting with get_person_profile (single-profile lookup) or the connection-filtering behavior, so sibling differentiation is only implicit.

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?

There is no when-to-use guidance at all: nothing says to use this for discovery versus get_person_profile for a known individual, nor when to combine it with get_company_employees. The agent must infer usage entirely from the name and schema.

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