linkedin-relay-mcp 3.7.0 → 3.9.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.
@@ -136,6 +136,19 @@ matched to its post for certain. A scheduled post is cancelled with `lnrelay del
136
136
  text changed with `lnrelay edit <urn> "<text>"` (both CLI, approved like any write). If `meta.state`
137
137
  is not `complete`, the list may be short — say so.
138
138
 
139
+ ### `experience` — live, 2 calls. The user's roles.
140
+ ```
141
+ experience
142
+ ```
143
+ Each role on their profile with its `positionId` and title. The id is what `lnrelay role edit` and
144
+ `lnrelay role remove` take.
145
+
146
+ ### `skills` — live, ~3 calls. The user's skills.
147
+ ```
148
+ skills
149
+ ```
150
+ Each skill on their profile with its `skillId` and name. The id is what `lnrelay skill remove` takes.
151
+
139
152
  ### `sync` — CLI-only. Fills the cache.
140
153
  ```
141
154
  lnrelay sync my-posts | lnrelay sync connections [--limit N] [--force]
@@ -203,6 +216,9 @@ Writes are **not on the MCP surface**. They exist only as CLI commands:
203
216
  | `lnrelay reply <comment-urn> "<text>"` | reply, nested under that comment |
204
217
  | `lnrelay edit <comment-urn \| share-urn \| ugcPost-urn> "<text>"` | change the text of their own comment or post |
205
218
  | `lnrelay edit headline\|about ("<text>" \| --file <path>)` | change their profile headline (max 220 characters) or About section |
219
+ | `lnrelay role add --title "…" --company "…" --start YYYY-MM [--end YYYY-MM \| --current] [--location "…"] [--description "…" \| --description-file <path>] [--notify]` | add a role to their Experience |
220
+ | `lnrelay role edit <position-id> [the same flags]` / `lnrelay role remove <position-id>` | change or remove one of their roles (ids from `experience`) |
221
+ | `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 |
206
222
  | `lnrelay react <urn> [--type X] [--remove]` | react to a post or comment |
207
223
  | `lnrelay delete <activity-urn \| comment-urn>` | delete their post or comment |
208
224
 
@@ -245,6 +261,9 @@ Things worth telling a user who asks:
245
261
  bound to both, so if the profile changed after the preview, re-plan. Every other profile field
246
262
  (name, location, current position) is sent back exactly as LinkedIn holds it, and the result is
247
263
  read back from the profile. About edits are refused while the About section has top skills set.
264
+ - Adding or editing a role never touches the headline. LinkedIn's own form would rewrite it to
265
+ "<title> at <company>"; this tool always turns that off. "Notify network" is off unless `--notify`.
266
+ The company is free text, not linked to a company page. A role with media attached is refused.
248
267
  - Scheduled posts are listed by `scheduled` (MCP and CLI), not by `my-posts`.
249
268
  - Editing a post replaces its whole text and LinkedIn marks it edited; pass the urn `share` printed
250
269
  (or `shareUrn` from `my-posts`), not the activity urn. An @mention in the old text is not kept.