linkedin-relay-mcp 3.12.1 → 3.13.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: linkedin-relay
3
- description: Research LinkedIn from the user's own account — search people and companies, hunt jobs with every filter LinkedIn has and collect their apply links, read profiles, read the chronological feed — and, through the lnrelay CLI, post (text, image or video), comment, reply, react, delete and edit the user's own profile (headline, About, roles, skills) under the approval mode the owner chose. Use when finding or evaluating people, companies, roles or job openings on LinkedIn, when the user wants job listings or application links, when reading what the user's network is posting, or when the user asks to post, engage or update their profile on LinkedIn. Not for messaging, connection requests or applying to jobs, which do not exist.
3
+ description: Research LinkedIn from the user's own account — find people by company, past company, school, place, title, degree or whose connections they are, search companies, hunt jobs with every filter LinkedIn has and collect their apply links, read profiles, read the chronological feed — and, through the lnrelay CLI, post (text, image or video), comment, reply, react, delete and edit the user's own profile (headline, About, roles, skills) under the approval mode the owner chose. Use when finding or evaluating people (who works or worked somewhere, alumni, people in a role or a city, someone's connections), companies, roles or job openings on LinkedIn, when the user wants job listings or application links, when reading what the user's network is posting, or when the user asks to post, engage or update their profile on LinkedIn. Not for messaging, connection requests or applying to jobs, which do not exist.
4
4
  ---
5
5
 
6
6
  # linkedin-relay
@@ -44,6 +44,44 @@ risk / budget free — check standing BEFORE spending
44
44
  Search rows already carry name, headline, location and URL. **Rank on those.** Calling `profile` on
45
45
  every search result is how a day's budget disappears in one request.
46
46
 
47
+ ## Finding people — the recipe
48
+
49
+ `people` is the people search with every filter LinkedIn has. Each call moves 50 people; a company
50
+ or school given by name costs one extra call to look up.
51
+
52
+ ```
53
+ 1. people_filters (optional, 1 call) ids and live counts for places, companies, schools,
54
+ industries, services — for this query
55
+ 2. people ALL keyword sets in ONE call, the filters, compact:true
56
+ 3. rank on headline, location, degree, insight — from the rows alone
57
+ 4. profile ONLY the 2-3 finalists, if the row is not enough
58
+ ```
59
+
60
+ A worked call, the shape to copy:
61
+
62
+ ```
63
+ people keywords:["engineering manager", "head of engineering"] company:["Microsoft"]
64
+ location:"Hungary" network:["2nd"] limit:100 compact:true
65
+ ```
66
+
67
+ From a shell: `lnrelay people "engineering manager" "head of engineering" --company Microsoft
68
+ --location Hungary --network 2nd --limit 100 --compact`.
69
+
70
+ - **Check `data.resolved`.** Company and school names, and `location`, are looked up to ids, and the
71
+ choice is reported there. A name can land on a different organisation ("Microsoft Cloud", a
72
+ similarly named school); if it did, re-run with the id from `people_filters` or the row it shows.
73
+ - **Ask the question with filters, not keywords.** "Who works at X" is `company`, not keywords;
74
+ "alumni of Y" is `school`; "in Z" is `location`; "people I can get an intro to" is `network:["2nd"]`;
75
+ "who does A know" is `connectionOf` with A's `id`. Keywords match anywhere on a profile.
76
+ - **`title` is free text against the current title**; `companyText`/`schoolText` are free text too,
77
+ for when there is no single organisation to name.
78
+ - **LinkedIn pages at most 1000 people per query.** `meta.servedLimit` means it claimed more: split
79
+ the query (by location, by company) rather than reporting the 1000 as everyone.
80
+ - **Not everyone is named.** LinkedIn may return people outside the user's network as
81
+ `"LinkedIn Member"` with no `url`. That is LinkedIn withholding them from this account; count them,
82
+ do not drop them silently, and say so.
83
+ - A row's `id` is the profile id: it goes into `connectionOf` / `followerOf`, and `profile` takes it.
84
+
47
85
  ## Job hunting — the recipe
48
86
 
49
87
  Jobs have their own commands, their own budget (150 job searches, 60 job reads a day) and their own
@@ -90,7 +128,7 @@ and `lnrelay job 4479248573 4475225930 4476083905`.
90
128
 
91
129
  ### `search` — cheap. The net.
92
130
  ```
93
- search kind:people|companies query:"<terms>" [limit:1-25] (jobs: use `jobs`)
131
+ search kind:people|companies query:"<terms>" [limit:1-25] (people with filters: `people`; jobs: `jobs`)
94
132
  ```
95
133
  Returns `{items, meta}`. Each item: `name`, `headline`, `location`, `url`, `urn`.
96
134
 
@@ -101,6 +139,34 @@ Out-of-network people come back as `name: "LinkedIn Member"` with a `/headless`
101
139
  LinkedIn behaviour, not a bug — LinkedIn will not name them to this account. Say so rather than
102
140
  presenting it as a data problem.
103
141
 
142
+ ### `people` — 1 search call per 50 people. People search with every filter.
143
+ ```
144
+ people [keywords:"<terms>" | ["<terms>", …]] [company:["<name|id>"]] [pastCompany:["<name|id>"]]
145
+ [school:["<name|id>"]] [location:"<place>" | geo:["<id>"]] [network:[1st|2nd|3rd+]]
146
+ [industry:[ids]] [language:["en"]] [service:[ids]] [title:"<text>"] [firstName] [lastName]
147
+ [companyText] [schoolText] [connectionOf:"<id>"] [followerOf:"<id>"] [openToVolunteer]
148
+ [filter:["key=v1,v2"]] [limit:1-1000 per keyword set] [start:N] [compact]
149
+ ```
150
+ CLI: `lnrelay people "<terms>" ["<more>" …] [--company "<name|id>" …] [--location "<place>"]
151
+ [--network 2nd] [--title "<text>"] [--limit N] [--compact]` — every option is in `lnrelay help`.
152
+ Company, past company and school take names or ids; repeat the flag for several names (a name may
153
+ contain commas), or comma-separate ids.
154
+
155
+ Each item: `id`, `name`, `headline`, `location`, `degree` (`1st`, `2nd`, `3rd+`, `out of network`),
156
+ `verified`, `insight` (mutual connections, followers, services offered), `url`, and `matched` with
157
+ several keyword sets. `compact` gives one line per person. `data.resolved` lists each name and the
158
+ id it became. Paging and `meta` work as for `jobs`, plus `meta.servedLimit` when LinkedIn claimed
159
+ more people than the 1000 it serves. Filters alone are a search: `connectionOf` with no keywords
160
+ lists that person's connections.
161
+
162
+ ### `people-filters` — 1 search call. The knobs, with ids.
163
+ ```
164
+ people_filters [keywords:"<terms>"] [any people filter]
165
+ ```
166
+ Every people filter for the query: its key, whether it takes ids or free text, and its options'
167
+ `value`, `label` and live `count`. The ids go into `geo`, `industry`, `service`, `company`, … or raw
168
+ `filter:["<key>=<value>"]`.
169
+
104
170
  ### `jobs` — 1 job-search call per 100 results. Job search with every filter.
105
171
  ```
106
172
  jobs keywords:"<terms>" | ["<terms>", "<terms>", …] [location:"<place>" | geoId:"<id>"] [distance:<miles>]
@@ -283,8 +349,9 @@ Every collection carries:
283
349
  | `state: complete` | every reference resolved; an empty `items` here genuinely means none |
284
350
  | `state: partial` | **some references failed to resolve** — the record is incomplete, not small |
285
351
  | `state: unknown` | we stopped at the limit and cannot prove exhaustion (people/company `search`, `post`, `reactions`) |
286
- | `next` | `jobs`: the `start` that continues this search; absent when the results ran out |
287
- | `searches` / `duplicates` | `jobs` with several keyword sets: each set's own count and state, and how many repeats were merged |
352
+ | `next` | `jobs` / `people`: the `start` that continues this search; absent when the results ran out |
353
+ | `servedLimit` | `people`: LinkedIn claimed more matches than it serves (1000 a query) — the list is NOT everyone; narrow the query |
354
+ | `searches` / `duplicates` | `jobs` / `people` with several keyword sets: each set's own count and state, and how many repeats were merged |
288
355
  | `unread` | `jobs --details` / `job`: jobs LinkedIn did not return in full — they are not closed, just unread |
289
356
  | `returnedCount` vs `claimedCount` | `claimed > 0` with `returned === 0` is a **failed fetch**, never "no results" |
290
357
  | `excludedCount` | ads and UI chrome deliberately dropped |
package/README.md CHANGED
@@ -9,7 +9,8 @@ Sibling to [`x-relay`](../x-relay), [`github-relay`](../github-relay) and
9
9
  ```bash
10
10
  npm i -g linkedin-relay-mcp
11
11
  lnrelay login # mint a session from your own Chrome
12
- lnrelay search people "rust developer" # ranked rows: name, headline, location, url
12
+ lnrelay people "engineering manager" --company Microsoft --location Hungary --compact
13
+ # people search with every filter, names looked up
13
14
  lnrelay jobs "frontend engineer" "AI agent developer" --workplace remote --posted week --compact
14
15
  # one merged job list across keyword sets
15
16
  lnrelay job 4479248573 4475225930 # full jobs, with their apply links
@@ -21,9 +22,10 @@ lnrelay local "rust" # then search it offline, free
21
22
 
22
23
  ## As an MCP server
23
24
 
24
- Nineteen read-only tools, so an agent does the reading. Writes are not on that surface at any price.
25
+ Twenty-one read-only tools, so an agent does the reading. Writes are not on that surface at any price.
25
26
  The bundled Claude Code skill (`.claude/skills/linkedin-relay/SKILL.md`) teaches an agent the
26
- funnels, the budget, and how to read `meta` — including a step-by-step job-hunting recipe.
27
+ funnels, the budget, and how to read `meta` — including step-by-step recipes for finding people and
28
+ for job hunting.
27
29
 
28
30
  ```bash
29
31
  claude mcp add linkedin-relay -s user -- bun "$(npm root -g)/linkedin-relay-mcp/dist/mcp-shim.js"
@@ -33,7 +35,8 @@ claude mcp add linkedin-relay -s user -- bun "$(npm root -g)/linkedin-relay-mcp/
33
35
 
34
36
  | | |
35
37
  |---|---|
36
- | `search` · `profile` · `feed` | the research surface — people and companies |
38
+ | `people` · `people-filters` | people search with every filter: company, past company, school, place, degree, title, someone's connections |
39
+ | `search` · `profile` · `feed` | one-page search of people or companies, a profile, your feed |
37
40
  | `jobs` · `job` · `job-filters` | job search with every filter, several keyword sets merged in one call, and apply links |
38
41
  | `post` · `reactions` | a post's comment thread, and who engaged |
39
42
  | `scheduled` · `experience` · `skills` | your queued posts, and your own roles and skills |
@@ -77,6 +80,25 @@ approved the way **you** chose with `lnrelay approval set` (only at a real termi
77
80
  There is no `--yes` and no environment variable. Every approval and outcome is logged to
78
81
  `~/.lnrelay/writes.jsonl`.
79
82
 
83
+ ## Finding people
84
+
85
+ ```bash
86
+ lnrelay people "engineering manager" "head of engineering" --company Microsoft --location Hungary --network 2nd --compact
87
+ lnrelay people --school "Budapest University of Technology" --company OTP --limit 200 # alumni at a company
88
+ lnrelay people --connection-of <profile-id> --network 2nd # their connections you are not yet connected to
89
+ lnrelay people-filters "frontend developer" --location Budapest # every filter, ids and counts
90
+ ```
91
+
92
+ - **Every filter the people search has:** current and past company, school, place, connection
93
+ degree, industry, profile language, service category, the connections or followers of a person,
94
+ open to volunteering, and free-text first name, last name, title, company and school.
95
+ - **Names, not ids.** `--company`, `--past-company`, `--school` and `--location` take names and look
96
+ them up; `data.resolved` says what each became, so a wrong match is visible.
97
+ - **50 people a call** (the page asks for 10). Asking for 100 is answered with an *empty success*, so
98
+ the tool never does. Several keyword sets merge by person, as for jobs.
99
+ - **LinkedIn serves at most 1000 people per query**, whatever it claims to have matched;
100
+ `meta.servedLimit` says when it held back, and the list is reported partial, not complete.
101
+
80
102
  ## Job hunting
81
103
 
82
104
  ```bash