linkedin-relay-mcp 3.18.0 → 3.20.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.
@@ -35,6 +35,7 @@ jobs 1 call / 100 — find jobs with filters; `job` reads finalists,
35
35
  search 1 call / 50 — posts, companies, groups, events, courses, products, services, schools
36
36
  ↓ pick 2-3 finalists from the rows alone, not by reading each one
37
37
  profile mid — deep-read ONLY the finalists
38
+ company mid — a company page in full; `posts:N` adds its newest posts
38
39
  feed mid — what the user's network is posting right now
39
40
  ↓ feed rows carry likes/comments counts — rank on those before reading a thread
40
41
  post exp — a post's comment thread
@@ -113,6 +114,11 @@ From a shell the same is
113
114
  `lnrelay jobs "frontend engineer" "AI agent developer" --location "European Union" --workplace remote --posted week --limit 200 --compact`
114
115
  and `lnrelay job 4479248573 4475225930 4476083905`.
115
116
 
117
+ - **Who to contact about a job: `job` with `team:true`** (`--team`). Each job gains `hiringTeam`:
118
+ name, profile id, profile URL, headline, connection degree, `role` ("Job poster") and `verified`.
119
+ It costs one page call per job (60 a day), so ask only for the finalists. `[]` means LinkedIn
120
+ shows no one for that job, which is most jobs; `hiringTeamError` means it could not be read.
121
+
116
122
  - **Put every keyword set in one `jobs` call**, never one call per keyword: the tool merges them by
117
123
  job id, so you read each job once and `job` reads it once. Separate calls leave the merging to you
118
124
  and spend reads twice on the same job.
@@ -361,6 +367,22 @@ CLI: `lnrelay my-items posts|learning|jobs [--stage …] [--compact]`. 1 page ca
361
367
  With no `stage`, all five stages (5 calls) and `meta.byStage`. LinkedIn does not check stage names:
362
368
  an empty stage and a misnamed one look the same, so trust `byStage` with that in mind.
363
369
 
370
+ ### `company` — a company page in full.
371
+ ```
372
+ company company:"<universal name | /company/ or /showcase/ URL | id>" | ["…", …] [posts:N] [compact]
373
+ ```
374
+ CLI: `lnrelay company microsoft [--posts 5] [--compact]`. One page call per company. Returns `id`,
375
+ `name`, `tagline`, `about`, `website`, `industry`, `type` ("Public Company"), `size` (the band the
376
+ company chose, "501-1,000"), `employeesOnLinkedIn` (members who list it, often far more than the
377
+ band), `followers`, `headquarters`, `specialties`, `locations`, `affiliated` and `showcasePages`
378
+ (`{id, name, url, followers}`), and `jobsUrl`.
379
+ - **The `id` is what the filters take:** `people company:[id]`, `jobs company:[id]`,
380
+ `search kind:posts fromCompany:[id]`. Find a company by topic with `search kind:companies` first.
381
+ - **`posts:N`** adds its N newest posts: a posts search from the company, sorted by date, on the
382
+ search budget (20 a call). `postsError` says why they could not be read; the company still comes.
383
+ - Several companies in one call return `{items, meta}`; a name LinkedIn does not know is listed in
384
+ `meta.unread` (`NOT_FOUND`). The same company by name and by id is listed once.
385
+
364
386
  ### `events` / `event` — the events page, and events in full.
365
387
  ```
366
388
  events [premium] [limit:N] [compact] event event:"<id | /events/ URL>" | ["<id>", …]
package/README.md CHANGED
@@ -44,6 +44,7 @@ claude mcp add linkedin-relay -s user -- bun "$(npm root -g)/linkedin-relay-mcp/
44
44
  | `post` · `reactions` | a post's comment thread, and who engaged |
45
45
  | `scheduled` · `experience` · `skills` | your queued posts, and your own roles and skills |
46
46
  | `my-items` | your saved posts, LinkedIn Learning courses, and the job tracker by stage |
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 |
47
48
  | `events` · `event` | the events page's recommended and Premium events, and any event in full: when, where, attendees, organiser, its site |
48
49
  | `network` | your My Network: connections, following, followers, pages, events, groups, invitations sent — or the count of each |
49
50
  | `inbox` · `messages` · `draft` · `drafts` | read your messages without marking them read; draft replies locally — nothing is ever sent |
@@ -151,6 +152,7 @@ lnrelay job-filters "frontend engineer" --location "European Union" # every fi
151
152
  lnrelay jobs "frontend engineer" "AI agent developer" "agent engineer" \
152
153
  --location "European Union" --workplace remote --posted week --limit 200 --compact
153
154
  lnrelay job <id> <id> <id> # finalists in full, apply links
155
+ lnrelay job <id> --team # + who posted it, who is hiring
154
156
  ```
155
157
 
156
158
  - **Every filter the jobs page has:** location or exact geo id, distance, date posted, experience,