linkedin-relay-mcp 3.6.1 → 3.8.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,13 @@ 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
+
139
146
  ### `sync` — CLI-only. Fills the cache.
140
147
  ```
141
148
  lnrelay sync my-posts | lnrelay sync connections [--limit N] [--force]
@@ -202,6 +209,9 @@ Writes are **not on the MCP surface**. They exist only as CLI commands:
202
209
  | `lnrelay comment <activity-urn> "<text>"` | comment on a post |
203
210
  | `lnrelay reply <comment-urn> "<text>"` | reply, nested under that comment |
204
211
  | `lnrelay edit <comment-urn \| share-urn \| ugcPost-urn> "<text>"` | change the text of their own comment or post |
212
+ | `lnrelay edit headline\|about ("<text>" \| --file <path>)` | change their profile headline (max 220 characters) or About section |
213
+ | `lnrelay role add --title "…" --company "…" --start YYYY-MM [--end YYYY-MM \| --current] [--location "…"] [--description "…" \| --description-file <path>] [--notify]` | add a role to their Experience |
214
+ | `lnrelay role edit <position-id> [the same flags]` / `lnrelay role remove <position-id>` | change or remove one of their roles (ids from `experience`) |
205
215
  | `lnrelay react <urn> [--type X] [--remove]` | react to a post or comment |
206
216
  | `lnrelay delete <activity-urn \| comment-urn>` | delete their post or comment |
207
217
 
@@ -240,6 +250,13 @@ Things worth telling a user who asks:
240
250
  and not on a post that already carries images, a video, a PDF or a poll). The plan names the card
241
251
  (`card "<title>" (<site>)`), or says LinkedIn has none. If the lookup fails nothing is posted; add
242
252
  `--no-card` to post the link as plain text.
253
+ - A profile edit's preview shows the current headline or About beside the new one. The approval is
254
+ bound to both, so if the profile changed after the preview, re-plan. Every other profile field
255
+ (name, location, current position) is sent back exactly as LinkedIn holds it, and the result is
256
+ read back from the profile. About edits are refused while the About section has top skills set.
257
+ - Adding or editing a role never touches the headline. LinkedIn's own form would rewrite it to
258
+ "<title> at <company>"; this tool always turns that off. "Notify network" is off unless `--notify`.
259
+ The company is free text, not linked to a company page. A role with media attached is refused.
243
260
  - Scheduled posts are listed by `scheduled` (MCP and CLI), not by `my-posts`.
244
261
  - Editing a post replaces its whole text and LinkedIn marks it edited; pass the urn `share` printed
245
262
  (or `shareUrn` from `my-posts`), not the activity urn. An @mention in the old text is not kept.