linkedin-relay-mcp 3.10.1 → 3.12.1
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.
- package/.claude/skills/linkedin-relay/SKILL.md +74 -13
- package/README.md +50 -7
- package/dist/cli.js +245 -85
- package/dist/cli.js.map +1 -1
- package/dist/index.js +6 -6
- package/dist/index.js.map +1 -1
- package/dist/mcp-shim.js +254 -91
- package/dist/mcp-shim.js.map +1 -1
- package/package.json +1 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: linkedin-relay
|
|
3
|
-
description: Research LinkedIn from the user's own account — search people
|
|
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.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# linkedin-relay
|
|
@@ -44,6 +44,48 @@ 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
|
+
## Job hunting — the recipe
|
|
48
|
+
|
|
49
|
+
Jobs have their own commands, their own budget (150 job searches, 60 job reads a day) and their own
|
|
50
|
+
funnel. Each call moves 100 jobs, so a whole hunt is a few dozen calls, not hundreds.
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
1. job_filters (optional, 1 call) the ids for company / industry / title / place, and live counts
|
|
54
|
+
2. jobs ALL keyword sets in ONE call, the same filters, compact:true
|
|
55
|
+
→ one merged list; `matched` says which sets found each job
|
|
56
|
+
3. rank on title, company, location, workplace, listed — from the rows alone
|
|
57
|
+
4. job ALL finalists in ONE call (a list of ids) → description + apply.url
|
|
58
|
+
5. report title · company · location · apply.url, and say how the list was cut
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
A worked call, the shape to copy:
|
|
62
|
+
|
|
63
|
+
```
|
|
64
|
+
jobs keywords:["frontend engineer", "AI agent developer", "agent engineer"]
|
|
65
|
+
location:"European Union" workplace:["remote"] posted:"week" limit:200 compact:true
|
|
66
|
+
job job:["4479248573", "4475225930", "4476083905"]
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
From a shell the same is
|
|
70
|
+
`lnrelay jobs "frontend engineer" "AI agent developer" --location "European Union" --workplace remote --posted week --limit 200 --compact`
|
|
71
|
+
and `lnrelay job 4479248573 4475225930 4476083905`.
|
|
72
|
+
|
|
73
|
+
- **Put every keyword set in one `jobs` call**, never one call per keyword: the tool merges them by
|
|
74
|
+
job id, so you read each job once and `job` reads it once. Separate calls leave the merging to you
|
|
75
|
+
and spend reads twice on the same job.
|
|
76
|
+
- **Use filters, not keywords, to narrow.** `posted:"week"`, `workplace`, `experience` and `geoId`
|
|
77
|
+
cut a list from hundreds to tens. Keywords are matched loosely by LinkedIn, so "AI agent
|
|
78
|
+
developer" also returns plain frontend jobs; a narrow keyword is not a narrow search.
|
|
79
|
+
- **`compact:true` for the wide pass** (one line per job, under half the size of the full rows), the full rows or
|
|
80
|
+
`job` only for what you will actually judge.
|
|
81
|
+
- **`details:true` only when you need every job's apply link** (for a full export, say). It costs one
|
|
82
|
+
read per 100 jobs and adds the employer, applicant count and apply link to every row; add
|
|
83
|
+
`description:true` only if you will read them all, because descriptions are long.
|
|
84
|
+
- **Most results are promoted** (often three in four). That is LinkedIn's ranking, not a filter we
|
|
85
|
+
can turn off; `promoted` on each row says which.
|
|
86
|
+
- **This tool cannot apply.** It finds the job and the link. `apply.type: "external"` is the
|
|
87
|
+
employer's own site; `"easy-apply"` is LinkedIn's form, done by the user in a browser.
|
|
88
|
+
|
|
47
89
|
## Commands
|
|
48
90
|
|
|
49
91
|
### `search` — cheap. The net.
|
|
@@ -59,20 +101,33 @@ Out-of-network people come back as `name: "LinkedIn Member"` with a `/headless`
|
|
|
59
101
|
LinkedIn behaviour, not a bug — LinkedIn will not name them to this account. Say so rather than
|
|
60
102
|
presenting it as a data problem.
|
|
61
103
|
|
|
62
|
-
### `jobs` — 1 job-search call per
|
|
104
|
+
### `jobs` — 1 job-search call per 100 results. Job search with every filter.
|
|
63
105
|
```
|
|
64
|
-
jobs keywords:"<terms>" [location:"<place>" | geoId:"<id>"] [distance:<miles>]
|
|
106
|
+
jobs keywords:"<terms>" | ["<terms>", "<terms>", …] [location:"<place>" | geoId:"<id>"] [distance:<miles>]
|
|
65
107
|
[posted:"24h|week|month|<N>h|<N>d"] [experience:[internship|entry|associate|mid-senior|director|executive]]
|
|
66
108
|
[type:[full-time|part-time|contract|temporary|volunteer|internship|other]]
|
|
67
109
|
[workplace:[on-site|remote|hybrid]] [easyApply] [under10] [verified] [inNetwork] [fairChance]
|
|
68
110
|
[company|industry|function|title|place:[ids]] [filter:["key=v1,v2"]] [sort:recent|relevant]
|
|
69
|
-
[limit:1-
|
|
111
|
+
[limit:1-1000 per keyword set] [start:N] [details] [description] [compact]
|
|
70
112
|
```
|
|
71
|
-
|
|
72
|
-
|
|
113
|
+
CLI: `lnrelay jobs "<terms>" ["<more terms>" …] [--location … | --geo …] [--workplace remote,hybrid]
|
|
114
|
+
[--posted week] [--experience mid-senior] [--easy-apply] [--limit N] [--details] [--compact]` — every
|
|
115
|
+
option is in `lnrelay help`; list options take commas or repeat.
|
|
73
116
|
|
|
74
|
-
|
|
75
|
-
|
|
117
|
+
Each item: `id`, `title`, `company`, `location`, `workplace`, `listed` (YYYY-MM-DD), `easyApply`,
|
|
118
|
+
`promoted`, `salary` (when the card shows one), `insights`, `url`, and `matched` with several
|
|
119
|
+
keyword sets. `compact` gives one line per job:
|
|
120
|
+
`<id> | <title> | <company> | <location> | <workplace> | <listed> | easy apply | promoted | matched: a + b`.
|
|
121
|
+
|
|
122
|
+
- **Several keyword sets in one call.** Pass `keywords` as a list: each set is searched with the
|
|
123
|
+
same filters, and the results are merged by job id. A job found by several sets comes back once,
|
|
124
|
+
with `matched` naming them; the most-matched come first. Treat that order as a hint, not a
|
|
125
|
+
ranking: LinkedIn matches keywords loosely ("AI agent developer" returns plain frontend jobs),
|
|
126
|
+
so a generic job can match every set. Rank on title and company.
|
|
127
|
+
`meta.searches` has each set's total, count, state and `next`; `meta.duplicates` is how many
|
|
128
|
+
repeats were merged. One set failing leaves the others, with `state: "failed"` in its entry.
|
|
129
|
+
- **Rank on the rows, then read the finalists with `job`.** `details` reads every row in full, 100
|
|
130
|
+
per job read, to add the apply link, applicants and employment type.
|
|
76
131
|
- **Check `data.location`.** A typed location is resolved by LinkedIn, and the place it chose is
|
|
77
132
|
reported there. "Vienna, Austria" resolved to one district of Vienna. Pass `geoId` for an exact
|
|
78
133
|
place; ids are in `job_filters` under `populatedPlace`.
|
|
@@ -80,13 +135,16 @@ Each item: `id`, `title`, `company`, `location`, `workplace`, `listed` (YYYY-MM-
|
|
|
80
135
|
batch, and `meta.state` is `complete` only when the results ran out. LinkedIn serves at most 1000
|
|
81
136
|
per search; narrow the query rather than paging deep.
|
|
82
137
|
- Job hunting has its own budget: 150 job-search calls and 60 job reads a day, apart from the
|
|
83
|
-
people and company `search`.
|
|
84
|
-
|
|
138
|
+
people and company `search`. A search call returns 100 jobs, so ten keyword sets of a few
|
|
139
|
+
hundred results each take about 30 calls. Reposts and recruiter copies of one role carry
|
|
140
|
+
different ids, so they are not merged: judge those by company, title and description.
|
|
85
141
|
|
|
86
|
-
### `job` — 1 job read.
|
|
142
|
+
### `job` — 1 job read per 100 jobs. Jobs, in full.
|
|
87
143
|
```
|
|
88
|
-
job job:"<id | /jobs/view/ URL | ?currentJobId= URL>"
|
|
144
|
+
job job:"<id | /jobs/view/ URL | ?currentJobId= URL>" or job job:["<id>", "<id>", …]
|
|
89
145
|
```
|
|
146
|
+
One id returns the job; a list returns `{items, meta}`, read 100 per call, so pass all your finalists
|
|
147
|
+
at once rather than one call each. `meta.unread` lists ids LinkedIn did not return.
|
|
90
148
|
`description`, `apply: {type: "external" | "easy-apply", url}`, `company`, `companyUrl`,
|
|
91
149
|
`location`, `workplace`, `employmentType`, `experienceLevel`, `industries`, `functions`, `listed`,
|
|
92
150
|
`expires`, `state` (`LISTED` or `CLOSED`), `applicants`, `ats` (the employer's applicant tracking
|
|
@@ -224,7 +282,10 @@ Every collection carries:
|
|
|
224
282
|
|---|---|
|
|
225
283
|
| `state: complete` | every reference resolved; an empty `items` here genuinely means none |
|
|
226
284
|
| `state: partial` | **some references failed to resolve** — the record is incomplete, not small |
|
|
227
|
-
| `state: unknown` | we stopped at the limit and cannot prove exhaustion (
|
|
285
|
+
| `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 |
|
|
288
|
+
| `unread` | `jobs --details` / `job`: jobs LinkedIn did not return in full — they are not closed, just unread |
|
|
228
289
|
| `returnedCount` vs `claimedCount` | `claimed > 0` with `returned === 0` is a **failed fetch**, never "no results" |
|
|
229
290
|
| `excludedCount` | ads and UI chrome deliberately dropped |
|
|
230
291
|
| `unknownCount` / `unknownTypes` | **LinkedIn shipped a shape we don't recognise.** Data is still returned, but the parser is behind. Worth telling the user. |
|
package/README.md
CHANGED
|
@@ -10,6 +10,9 @@ Sibling to [`x-relay`](../x-relay), [`github-relay`](../github-relay) and
|
|
|
10
10
|
npm i -g linkedin-relay-mcp
|
|
11
11
|
lnrelay login # mint a session from your own Chrome
|
|
12
12
|
lnrelay search people "rust developer" # ranked rows: name, headline, location, url
|
|
13
|
+
lnrelay jobs "frontend engineer" "AI agent developer" --workplace remote --posted week --compact
|
|
14
|
+
# one merged job list across keyword sets
|
|
15
|
+
lnrelay job 4479248573 4475225930 # full jobs, with their apply links
|
|
13
16
|
lnrelay feed --compact # your feed, with engagement counts
|
|
14
17
|
lnrelay post <activity-urn> # a post's comment thread
|
|
15
18
|
lnrelay sync connections
|
|
@@ -18,7 +21,9 @@ lnrelay local "rust" # then search it offline, free
|
|
|
18
21
|
|
|
19
22
|
## As an MCP server
|
|
20
23
|
|
|
21
|
-
|
|
24
|
+
Nineteen read-only tools, so an agent does the reading. Writes are not on that surface at any price.
|
|
25
|
+
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.
|
|
22
27
|
|
|
23
28
|
```bash
|
|
24
29
|
claude mcp add linkedin-relay -s user -- bun "$(npm root -g)/linkedin-relay-mcp/dist/mcp-shim.js"
|
|
@@ -28,11 +33,15 @@ claude mcp add linkedin-relay -s user -- bun "$(npm root -g)/linkedin-relay-mcp/
|
|
|
28
33
|
|
|
29
34
|
| | |
|
|
30
35
|
|---|---|
|
|
31
|
-
| `search` · `profile` · `feed` | the research surface — people
|
|
36
|
+
| `search` · `profile` · `feed` | the research surface — people and companies |
|
|
37
|
+
| `jobs` · `job` · `job-filters` | job search with every filter, several keyword sets merged in one call, and apply links |
|
|
32
38
|
| `post` · `reactions` | a post's comment thread, and who engaged |
|
|
39
|
+
| `scheduled` · `experience` · `skills` | your queued posts, and your own roles and skills |
|
|
33
40
|
| `sync` · `local` · `connections` · `my-posts` | fill a local cache, then query it for free |
|
|
34
41
|
| `whoami` · `doctor` · `risk` · `budget` · `cache-status` | session, standing and spend |
|
|
35
|
-
| `
|
|
42
|
+
| `share` · `comment` · `reply` · `edit` · `react` · `delete` | writes to your feed — OAuth when available, private API otherwise |
|
|
43
|
+
| `edit headline\|about` · `role` · `skill` | writes to your own profile |
|
|
44
|
+
| `oauth` · `approval` | the write credential, and how writes are approved |
|
|
36
45
|
| `purge` | delete cached data |
|
|
37
46
|
|
|
38
47
|
Every command prints a JSON envelope on stdout. `--compact` and `--fields a,b` trim the output;
|
|
@@ -56,8 +65,41 @@ private API using the same session your reads use. It breaches §8.2 and puts th
|
|
|
56
65
|
the prompt says so, names the transport, and asks anyway. An expired OAuth token is never silently
|
|
57
66
|
demoted to it. Reasoning and alternatives: **[docs/DECISION-writes.md](docs/DECISION-writes.md)**.
|
|
58
67
|
|
|
59
|
-
Every write
|
|
60
|
-
|
|
68
|
+
Every write shows exactly what it will send, over which surface, and how reversible it is, and is
|
|
69
|
+
approved the way **you** chose with `lnrelay approval set` (only at a real terminal):
|
|
70
|
+
|
|
71
|
+
| mode | how a write is approved |
|
|
72
|
+
|---|---|
|
|
73
|
+
| `interactive` (default) | a token typed at the terminal; no TTY means no write and no network call |
|
|
74
|
+
| `agent` | `--plan` returns a preview and a token; you approve it in chat; `--confirm <token>` runs exactly that content |
|
|
75
|
+
| `unattended` | runs as given |
|
|
76
|
+
|
|
77
|
+
There is no `--yes` and no environment variable. Every approval and outcome is logged to
|
|
78
|
+
`~/.lnrelay/writes.jsonl`.
|
|
79
|
+
|
|
80
|
+
## Job hunting
|
|
81
|
+
|
|
82
|
+
```bash
|
|
83
|
+
lnrelay job-filters "frontend engineer" --location "European Union" # every filter, its ids and counts
|
|
84
|
+
lnrelay jobs "frontend engineer" "AI agent developer" "agent engineer" \
|
|
85
|
+
--location "European Union" --workplace remote --posted week --limit 200 --compact
|
|
86
|
+
lnrelay job <id> <id> <id> # finalists in full, apply links
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
- **Every filter the jobs page has:** location or exact geo id, distance, date posted, experience,
|
|
90
|
+
job type, workplace, Easy Apply, under 10 applicants, verified, in your network, fair chance,
|
|
91
|
+
company, industry, function, title, city, sort — and any other by its own name with
|
|
92
|
+
`--filter key=value`.
|
|
93
|
+
- **Several keyword sets, one list.** Each set is searched with the same filters and the results are
|
|
94
|
+
merged by job id: a job found by three sets comes back once, saying which. Live, four sets of 200
|
|
95
|
+
gave 800 rows, of which 280 were repeats.
|
|
96
|
+
- **100 jobs a call, both ways.** Searches ask for 100 results a page (the browser asks for 25), and
|
|
97
|
+
`job` / `--details` read up to 100 jobs in full in one batch call. 250 jobs with every apply link
|
|
98
|
+
took 6 calls.
|
|
99
|
+
- **The apply link** is the employer's own site (`external`) or LinkedIn's Easy Apply. This tool
|
|
100
|
+
finds jobs; it does not apply to them.
|
|
101
|
+
- Job hunting has its own daily budget — 150 search calls, 60 job reads — so it neither uses up nor
|
|
102
|
+
is stopped by people and company research.
|
|
61
103
|
|
|
62
104
|
## Design in one screen
|
|
63
105
|
|
|
@@ -76,7 +118,8 @@ surface, and how reversible it is — no TTY means no write and no network call.
|
|
|
76
118
|
`claimedCount`; a claimed-but-empty response is an error, not "no results".
|
|
77
119
|
- **Third-party data is not cached by default.** When retained, a 30-day TTL swept on the read path;
|
|
78
120
|
on expiry the body dies and only an identity stub survives.
|
|
79
|
-
- **Writes
|
|
121
|
+
- **Writes are approved under a mode only the owner can set** — at a terminal, behind a typed token.
|
|
122
|
+
An agent can plan a write but never choose its own approval.
|
|
80
123
|
- **Single account by construction** — multi-account isn't disallowed, it's unrepresentable.
|
|
81
124
|
|
|
82
125
|
Full reasoning: **[docs/DESIGN.md](docs/DESIGN.md)** · Engine internals:
|
|
@@ -109,7 +152,7 @@ position under argument. The convergence and the full disagreement record are in
|
|
|
109
152
|
## Development
|
|
110
153
|
|
|
111
154
|
```bash
|
|
112
|
-
bun run check # typecheck + lint +
|
|
155
|
+
bun run check # typecheck + lint + tests
|
|
113
156
|
bun run build
|
|
114
157
|
bun run dev -- <command>
|
|
115
158
|
```
|