linkedin-relay-mcp 3.8.0 → 3.10.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.
- package/.claude/skills/linkedin-relay/SKILL.md +49 -1
- package/dist/cli.js +1023 -150
- package/dist/cli.js.map +1 -1
- package/dist/index.js +46 -10
- package/dist/index.js.map +1 -1
- package/dist/mcp-shim.js +837 -75
- package/dist/mcp-shim.js.map +1 -1
- package/package.json +1 -1
|
@@ -47,7 +47,7 @@ every search result is how a day's budget disappears in one request.
|
|
|
47
47
|
|
|
48
48
|
### `search` — cheap. The net.
|
|
49
49
|
```
|
|
50
|
-
search kind:people|companies
|
|
50
|
+
search kind:people|companies query:"<terms>" [limit:1-25] (jobs: use `jobs`)
|
|
51
51
|
```
|
|
52
52
|
Returns `{items, meta}`. Each item: `name`, `headline`, `location`, `url`, `urn`.
|
|
53
53
|
|
|
@@ -58,6 +58,47 @@ Out-of-network people come back as `name: "LinkedIn Member"` with a `/headless`
|
|
|
58
58
|
LinkedIn behaviour, not a bug — LinkedIn will not name them to this account. Say so rather than
|
|
59
59
|
presenting it as a data problem.
|
|
60
60
|
|
|
61
|
+
### `jobs` — 1 search call per 25 results. Job search with every filter.
|
|
62
|
+
```
|
|
63
|
+
jobs keywords:"<terms>" [location:"<place>" | geoId:"<id>"] [distance:<miles>]
|
|
64
|
+
[posted:"24h|week|month|<N>h|<N>d"] [experience:[internship|entry|associate|mid-senior|director|executive]]
|
|
65
|
+
[type:[full-time|part-time|contract|temporary|volunteer|internship|other]]
|
|
66
|
+
[workplace:[on-site|remote|hybrid]] [easyApply] [under10] [verified] [inNetwork] [fairChance]
|
|
67
|
+
[company|industry|function|title|place:[ids]] [filter:["key=v1,v2"]] [sort:recent|relevant]
|
|
68
|
+
[limit:1-100] [start:N] [details] [description] [compact]
|
|
69
|
+
```
|
|
70
|
+
Each item: `id`, `title`, `company`, `location`, `workplace`, `listed` (YYYY-MM-DD), `easyApply`,
|
|
71
|
+
`promoted`, `salary` (when the card shows one), `insights`, `url`. `compact` gives one line per job.
|
|
72
|
+
|
|
73
|
+
- **Rank on the rows, then read the finalists with `job`.** `details` reads *every* row (1 profile
|
|
74
|
+
call each, 30 a day) to add the apply link, applicants and employment type.
|
|
75
|
+
- **Check `data.location`.** A typed location is resolved by LinkedIn, and the place it chose is
|
|
76
|
+
reported there. "Vienna, Austria" resolved to one district of Vienna. Pass `geoId` for an exact
|
|
77
|
+
place; ids are in `job_filters` under `populatedPlace`.
|
|
78
|
+
- **Paging:** `meta.claimedCount` is LinkedIn's total, `meta.next` is the `start` for the next
|
|
79
|
+
batch, and `meta.state` is `complete` only when the results ran out. LinkedIn serves at most 1000
|
|
80
|
+
per search; narrow the query rather than paging deep.
|
|
81
|
+
- For several searches (keyword variants), keep each one narrow with filters. Every 25 rows costs a
|
|
82
|
+
search call, and the day has 25.
|
|
83
|
+
|
|
84
|
+
### `job` — 1 profile call. One job, in full.
|
|
85
|
+
```
|
|
86
|
+
job job:"<id | /jobs/view/ URL | ?currentJobId= URL>"
|
|
87
|
+
```
|
|
88
|
+
`description`, `apply: {type: "external" | "easy-apply", url}`, `company`, `companyUrl`,
|
|
89
|
+
`location`, `workplace`, `employmentType`, `experienceLevel`, `industries`, `functions`, `listed`,
|
|
90
|
+
`expires`, `state` (`LISTED` or `CLOSED`), `applicants`, `ats` (the employer's applicant tracking
|
|
91
|
+
system), and `applied` / `saved` for this user. For an external application, `apply.url` goes to
|
|
92
|
+
the employer's own site.
|
|
93
|
+
|
|
94
|
+
### `job-filters` — 1 search call. The knobs, with ids.
|
|
95
|
+
```
|
|
96
|
+
job_filters keywords:"<terms>" [location | geoId] [any jobs filter]
|
|
97
|
+
```
|
|
98
|
+
Every filter LinkedIn offers for this query, each with its options' `value`, `label` and live
|
|
99
|
+
`count`. These values go into `company`, `industry`, `function`, `title`, `place`, or raw
|
|
100
|
+
`filter:["<key>=<value>,…"]` for anything else (benefits, commitments, …).
|
|
101
|
+
|
|
61
102
|
### `profile` — mid. Read only the finalists.
|
|
62
103
|
```
|
|
63
104
|
profile id:"<public-id|urn|linkedin.com/in/… URL>"
|
|
@@ -143,6 +184,12 @@ experience
|
|
|
143
184
|
Each role on their profile with its `positionId` and title. The id is what `lnrelay role edit` and
|
|
144
185
|
`lnrelay role remove` take.
|
|
145
186
|
|
|
187
|
+
### `skills` — live, ~3 calls. The user's skills.
|
|
188
|
+
```
|
|
189
|
+
skills
|
|
190
|
+
```
|
|
191
|
+
Each skill on their profile with its `skillId` and name. The id is what `lnrelay skill remove` takes.
|
|
192
|
+
|
|
146
193
|
### `sync` — CLI-only. Fills the cache.
|
|
147
194
|
```
|
|
148
195
|
lnrelay sync my-posts | lnrelay sync connections [--limit N] [--force]
|
|
@@ -212,6 +259,7 @@ Writes are **not on the MCP surface**. They exist only as CLI commands:
|
|
|
212
259
|
| `lnrelay edit headline\|about ("<text>" \| --file <path>)` | change their profile headline (max 220 characters) or About section |
|
|
213
260
|
| `lnrelay role add --title "…" --company "…" --start YYYY-MM [--end YYYY-MM \| --current] [--location "…"] [--description "…" \| --description-file <path>] [--notify]` | add a role to their Experience |
|
|
214
261
|
| `lnrelay role edit <position-id> [the same flags]` / `lnrelay role remove <position-id>` | change or remove one of their roles (ids from `experience`) |
|
|
262
|
+
| `lnrelay skill add "<name>"` / `lnrelay skill remove <skill-id>` | add a skill (free text, linked to nothing) or remove one (ids from `skills`); removing drops its endorsements |
|
|
215
263
|
| `lnrelay react <urn> [--type X] [--remove]` | react to a post or comment |
|
|
216
264
|
| `lnrelay delete <activity-urn \| comment-urn>` | delete their post or comment |
|
|
217
265
|
|