linkedin-relay-mcp 3.16.0 → 3.17.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.
@@ -348,6 +348,23 @@ experience
348
348
  Each role on their profile with its `positionId` and title. The id is what `lnrelay role edit` and
349
349
  `lnrelay role remove` take.
350
350
 
351
+ ### `events` / `event` — the events page, and events in full.
352
+ ```
353
+ events [premium] [limit:N] [compact] event event:"<id | /events/ URL>" | ["<id>", …]
354
+ ```
355
+ CLI: `lnrelay events [--premium] [--compact]`, `lnrelay event <id|url> [...]`. Three ways in:
356
+ - **By topic:** `search kind:events keywords:"…"` (50 a call; rows: name, when, where • organiser).
357
+ It returns past events too and takes no date filter: check `state` with `event` (`FUTURE` or
358
+ `ONGOING`) before recommending one.
359
+ - **What LinkedIn recommends:** `events` — the events page's own list, plus its Premium LinkedIn Live
360
+ events (`premium: true`). One call. Rows: `id`, `name`, `when`, `organizer`, `attendees`, `url`.
361
+ - **One in full:** `event` — `when`, `start`/`end` (ISO), `timeZone`, `state` (`FUTURE`, `ONGOING`,
362
+ `PAST`), `cancelled`, `online`, `place` (city, region, country), `site` (its own registration
363
+ page), `attendees`, `organizer`, `description`, and `you` when the user has responded. One call each.
364
+
365
+ Times shown (`when`) are as LinkedIn displays them to the user, in their language and time zone; use
366
+ `start`/`end` for anything computed. LinkedIn's "not interested" default is not reported as a reply.
367
+
351
368
  ### `network` — the user's My Network. Read only.
352
369
  ```
353
370
  network [list:connections|following|followers|pages|events|groups|invitations] [limit:N] [start:N] [compact]
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-seven tools, none of which writes to LinkedIn, so an agent does the reading. Writes are not on that surface at any price.
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.
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
+ | `events` · `event` | the events page's recommended and Premium events, and any event in full: when, where, attendees, organiser, its site |
46
47
  | `network` | your My Network: connections, following, followers, pages, events, groups, invitations sent — or the count of each |
47
48
  | `inbox` · `messages` · `draft` · `drafts` | read your messages without marking them read; draft replies locally — nothing is ever sent |
48
49
  | `sync` · `local` · `connections` · `my-posts` | fill a local cache, then query it for free |