linkedin-relay-mcp 3.25.0 → 3.26.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.
@@ -118,6 +118,17 @@ and `lnrelay job 4479248573 4475225930 4476083905`.
118
118
  name, profile id, profile URL, headline, connection degree, `role` ("Job poster") and `verified`.
119
119
  It costs one page call per job (60 a day), so ask only for the finalists. `[]` means LinkedIn
120
120
  shows no one for that job, which is most jobs; `hiringTeamError` means it could not be read.
121
+ - **How crowded a job is, and the company behind it (Premium): `job` with `insights:true`**
122
+ (`--insights`). Each job gains `premium`: `applicants` {`total` who clicked apply, `lastDay`,
123
+ `seniority` [{level, share, count}], `education` [{degree, share}]} and `company` {`name`,
124
+ `headcount` {asOf, now, sixMonthsAgo, yearAgo, twoYearsAgo, `growth1y` in %}, `function` (the
125
+ job's own function there: name and the same counts), `medianTenure`, `competitors` [{name,
126
+ industry, url}], and LinkedIn's generated `hiring`, `priorities` and `landscape` text}. One more
127
+ job read per job (60 a day), so finalists only. `premiumError` says why it could not be read.
128
+ - **Jobs where the user would stand out (Premium): `jobs` with `topApplicant:true`**
129
+ (`--top-applicant`). LinkedIn's own list of jobs where it says the user would be a top
130
+ applicant: job cards as `jobs` returns them, 100 a call, usually all in one. It takes no
131
+ keywords, location or filters; rank and read finalists as with any search.
121
132
 
122
133
  - **Put every keyword set in one `jobs` call**, never one call per keyword: the tool merges them by
123
134
  job id, so you read each job once and `job` reads it once. Separate calls leave the merging to you
@@ -457,15 +468,19 @@ count), and items as `kind` (LinkedIn's own name, e.g. `FOLLOW_PAGE_HERO`, `LEAR
457
468
  ### `viewers` — 2 page calls. Who viewed the user's profile.
458
469
  ```
459
470
  viewers [compact]
460
- ```
461
- CLI: `lnrelay viewers [--compact]`. As the user's profile-views page shows it: `total` over
462
- `period` (LinkedIn's words, past 90 days), `privateViewers` (private-mode viewers are a count, no
463
- names), and `items`: named viewers as `name`, `id` (what `profile`, `messages` and `connectionOf`
464
- take), `url`, `degree`, `headline`, `viewed` ("2d ago"); anonymous ones as `anonymous: true`,
465
- `description` ("Founder in the Software industry from Budapest"), `viewed`, `searchUrl`.
466
- - A free account is shown up to 3 viewers, so `meta.state` is `partial` whenever `total` is higher.
467
- The rest is behind Premium; this does not get around that.
468
- - Degree and times come in the session's language, which may not be English.
471
+ viewers days:365
472
+ ```
473
+ CLI: `lnrelay viewers [--days 7|14|28|90|365] [--compact]`. As the user's profile-views page shows
474
+ it: `total`, `privateViewers` (private-mode viewers are a count, no names), and `items`: named
475
+ viewers as `name`, `id` (what `profile`, `messages` and `connectionOf` take), `url`, `degree`,
476
+ `headline`, `viewed` ("2d ago"); anonymous ones as `anonymous: true`, `description` ("Founder in the
477
+ Software industry from Budapest"), `viewed`, `searchUrl`.
478
+ - **Premium** names every viewer in the range and takes `days` (default the page's 90; 365 is the
479
+ longest). It adds `highlights` [{label, value}]: top location, industry and company, and
480
+ `companies` [{name, share}]: where viewers work, with their share in percent.
481
+ - A free account is shown up to 3 viewers and the total is labelled with its `period`.
482
+ - `meta.state` is `complete` only when the named and private viewers add up to `total`.
483
+ - Degree, labels and times come in the session's language, which may not be English.
469
484
 
470
485
  ### `inbox` — 1 page call per 20 conversations. The user's messages.
471
486
  ```
package/README.md CHANGED
@@ -47,7 +47,7 @@ claude mcp add linkedin-relay -s user -- bun "$(npm root -g)/linkedin-relay-mcp/
47
47
  | `company` | a company page in full: about, website, industry, size, employees, followers, headquarters, specialties, locations, affiliated and showcase pages — and, with `--posts N`, its newest posts |
48
48
  | `events` · `event` | the events page's recommended and Premium events, and any event in full: when, where, attendees, organiser, its site |
49
49
  | `network` | your My Network: connections, following, followers, pages, events, groups, invitations sent — or the count of each |
50
- | `viewers` | who viewed your profile: the total, the viewers LinkedIn names (3 on a free account), anonymous ones, the private-mode count |
50
+ | `viewers` | who viewed your profile: the total, the viewers LinkedIn names (3 on a free account, all with Premium), anonymous ones, the private-mode count; with Premium, `--days` up to 365 and the top location, industry and companies of your viewers |
51
51
  | `notifications` | your notifications, newest first, read or not — without marking them seen |
52
52
  | `inbox` · `messages` · `draft` · `drafts` | read your messages without marking them read; draft replies locally — nothing is ever sent |
53
53
  | `sync` · `local` · `connections` · `my-posts` | fill a local cache, then query it for free |
@@ -155,6 +155,8 @@ lnrelay jobs "frontend engineer" "AI agent developer" "agent engineer" \
155
155
  --location "European Union" --workplace remote --posted week --limit 200 --compact
156
156
  lnrelay job <id> <id> <id> # finalists in full, apply links
157
157
  lnrelay job <id> --team # + who posted it, who is hiring
158
+ lnrelay job <id> --insights # Premium: who applied, company headcount and insights
159
+ lnrelay jobs --top-applicant --compact # Premium: jobs where you'd be a top applicant
158
160
  ```
159
161
 
160
162
  - **Every filter the jobs page has:** location or exact geo id, distance, date posted, experience,