linkedin-relay-mcp 3.17.0 → 3.19.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 — find people by company, past company, school, place, title, degree or whose connections they are, search posts, companies, groups, events, courses, products, services and schools, 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 looking at the user's own network (connections, followers, who they follow, invitations they sent), when finding or evaluating people (who works or worked somewhere, alumni, people in a role or a city, someone's connections), companies, groups, events, courses, posts on a topic, roles or job openings on LinkedIn, when the user wants job listings or application links, when reading what the user's network is posting, when the user wants to read their LinkedIn messages or draft replies to them, or when the user asks to post, engage or update their profile on LinkedIn. Cannot send messages, connect, or apply to jobs: those 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 posts, companies, groups, events, courses, products, services and schools, 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 looking at the user's own network (connections, followers, who they follow, invitations they sent) or their saved items (saved posts, courses, the job tracker), when finding or evaluating people (who works or worked somewhere, alumni, people in a role or a city, someone's connections), companies, groups, events, courses, posts on a topic, roles or job openings on LinkedIn, when the user wants job listings or application links, when reading what the user's network is posting, when the user wants to read their LinkedIn messages or draft replies to them, or when the user asks to post, engage or update their profile on LinkedIn. Cannot send messages, connect, or apply to jobs: those do not exist.
4
4
  ---
5
5
 
6
6
  # linkedin-relay
@@ -113,6 +113,11 @@ From a shell the same is
113
113
  `lnrelay jobs "frontend engineer" "AI agent developer" --location "European Union" --workplace remote --posted week --limit 200 --compact`
114
114
  and `lnrelay job 4479248573 4475225930 4476083905`.
115
115
 
116
+ - **Who to contact about a job: `job` with `team:true`** (`--team`). Each job gains `hiringTeam`:
117
+ name, profile id, profile URL, headline, connection degree, `role` ("Job poster") and `verified`.
118
+ It costs one page call per job (60 a day), so ask only for the finalists. `[]` means LinkedIn
119
+ shows no one for that job, which is most jobs; `hiringTeamError` means it could not be read.
120
+
116
121
  - **Put every keyword set in one `jobs` call**, never one call per keyword: the tool merges them by
117
122
  job id, so you read each job once and `job` reads it once. Separate calls leave the merging to you
118
123
  and spend reads twice on the same job.
@@ -348,6 +353,19 @@ experience
348
353
  Each role on their profile with its `positionId` and title. The id is what `lnrelay role edit` and
349
354
  `lnrelay role remove` take.
350
355
 
356
+ ### `my-items` — saved posts, learning, the job tracker.
357
+ ```
358
+ my_items list:posts|learning|jobs [stage:saved|in-progress|applied|interview|archived] [limit:N] [compact]
359
+ ```
360
+ CLI: `lnrelay my-items posts|learning|jobs [--stage …] [--compact]`. 1 page call per 10 items.
361
+ - `posts`: what the user saved — `id` (the post urn: `post` reads its thread), `author`,
362
+ `authorHeadline`, `posted`, `text`, `url`.
363
+ - `learning`: their courses — `name`, `length`, `detail` (instructor, released), `progress`.
364
+ - `jobs`: the job tracker — `id` (`job` reads it in full: description and apply link), `title`,
365
+ `company`, `location`, `workplace`, `stage`, `note` (e.g. "No longer accepting applications").
366
+ With no `stage`, all five stages (5 calls) and `meta.byStage`. LinkedIn does not check stage names:
367
+ an empty stage and a misnamed one look the same, so trust `byStage` with that in mind.
368
+
351
369
  ### `events` / `event` — the events page, and events in full.
352
370
  ```
353
371
  events [premium] [limit:N] [compact] event event:"<id | /events/ URL>" | ["<id>", …]
package/README.md CHANGED
@@ -24,7 +24,7 @@ lnrelay local "rust" # then search it offline, free
24
24
 
25
25
  ## As an MCP server
26
26
 
27
- Twenty-nine tools, none of which writes to LinkedIn, so an agent does the reading. Writes are not on that surface at any price.
27
+ Thirty tools, none of which writes to LinkedIn, so an agent does the reading. Writes are not on that surface at any price.
28
28
  The bundled Claude Code skill (`.claude/skills/linkedin-relay/SKILL.md`) teaches an agent the
29
29
  funnels, the budget, and how to read `meta` — including step-by-step recipes for finding people and
30
30
  for job hunting.
@@ -43,6 +43,7 @@ claude mcp add linkedin-relay -s user -- bun "$(npm root -g)/linkedin-relay-mcp/
43
43
  | `jobs` · `job` · `job-filters` | job search with every filter, several keyword sets merged in one call, and apply links |
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
+ | `my-items` | your saved posts, LinkedIn Learning courses, and the job tracker by stage |
46
47
  | `events` · `event` | the events page's recommended and Premium events, and any event in full: when, where, attendees, organiser, its site |
47
48
  | `network` | your My Network: connections, following, followers, pages, events, groups, invitations sent — or the count of each |
48
49
  | `inbox` · `messages` · `draft` · `drafts` | read your messages without marking them read; draft replies locally — nothing is ever sent |
@@ -150,6 +151,7 @@ lnrelay job-filters "frontend engineer" --location "European Union" # every fi
150
151
  lnrelay jobs "frontend engineer" "AI agent developer" "agent engineer" \
151
152
  --location "European Union" --workplace remote --posted week --limit 200 --compact
152
153
  lnrelay job <id> <id> <id> # finalists in full, apply links
154
+ lnrelay job <id> --team # + who posted it, who is hiring
153
155
  ```
154
156
 
155
157
  - **Every filter the jobs page has:** location or exact geo id, distance, date posted, experience,